CVE-2026-92133: Vulnerability in Jenkins Project Jenkins GitLab Plugin
Jenkins GitLab Plugin 1.2149.vcfc32c82b_f7f and earlier caches the GitLab API client built for alternative GitLab API token credentials under a cache key derived from the credentials ID alone, omitting the folder in which the credentials are resolved, allowing attackers with Item/Configure permission to access GitLab API token credentials they are not entitled to use.
AI Analysis
Technical Summary
Jenkins GitLab Plugin versions up to 1.2149.vcfc32c82b_f7f contain a vulnerability where the caching mechanism for GitLab API clients uses a cache key derived only from the credentials ID, omitting the folder context in which the credentials are resolved. This flaw allows attackers who have Item/Configure permission to access GitLab API token credentials associated with other folders, thereby bypassing intended access restrictions.
Potential Impact
Attackers with Item/Configure permission can gain unauthorized access to GitLab API token credentials they are not entitled to use. This could lead to unauthorized actions performed via the GitLab API under the context of those credentials.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
CVE-2026-92133: Vulnerability in Jenkins Project Jenkins GitLab Plugin
Description
Jenkins GitLab Plugin 1.2149.vcfc32c82b_f7f and earlier caches the GitLab API client built for alternative GitLab API token credentials under a cache key derived from the credentials ID alone, omitting the folder in which the credentials are resolved, allowing attackers with Item/Configure permission to access GitLab API token credentials they are not entitled to use.
CVSS v3.1
Score 5.4medium
Affected software
Jenkins Project
Jenkins GitLab Plugin
pkg:github/jenkinsci/gitlab-pluginRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Jenkins GitLab Plugin versions up to 1.2149.vcfc32c82b_f7f contain a vulnerability where the caching mechanism for GitLab API clients uses a cache key derived only from the credentials ID, omitting the folder context in which the credentials are resolved. This flaw allows attackers who have Item/Configure permission to access GitLab API token credentials associated with other folders, thereby bypassing intended access restrictions.
Potential Impact
Attackers with Item/Configure permission can gain unauthorized access to GitLab API token credentials they are not entitled to use. This could lead to unauthorized actions performed via the GitLab API under the context of those credentials.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- jenkins
- Date Reserved
- 2026-09-15T16:29:44.795Z
- State
- PUBLISHED
Threat ID: 6aaaa17355bf5e2cf5b35d5e
Added to database: 09/16/2026, 14:02:27 UTC
Last enriched: 09/16/2026, 14:17:27 UTC
Last updated: 09/17/2026, 02:03:49 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.