CVE-2026-84664: Jenkins GitLab Plugin vulnerability

Published Sep 2, 2026
·
Updated

Jenkins GitLab Plugin 1.9.16 and earlier allows overwriting the global GitLab connection configuration through Stapler data binding, allowing attackers to connect to an attacker-specified URL using GitLab API tokens already configured by administrators.

Affected Software

1 affected component
Jenkins GitLab Plugin<=1.9.16

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade jenkins/gitlab-plugin to a version that resolves this vulnerability.

    Fixed in 1.9.16

Event History

Sep 2, 2026
CVE Published
via MITRE·03:40 PM
Data Sourced
via MITRE·03:40 PM
Description
Data Sourced
via NVD·04:17 PM
Description

Frequently Asked Questions

1

Which plugin versions should be treated as affected?

Jenkins GitLab Plugin version 1.9.16 and earlier are affected.

2

What existing configuration makes this issue impactful?

The impact relies on GitLab API tokens that administrators have already configured in the global GitLab connection configuration. Those tokens can be used when the connection is redirected to an attacker-specified URL.

3

Is the configuration targeted by this issue global or limited to an individual job?

The issue affects the global GitLab connection configuration.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203