Openid Connect ProviderApplication · Jenkins
CVE-2025-47884
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Jenkins OpenID Connect Provider Plugin 96.vee8ed882ec4d and earlier the generation of build ID Tokens uses potentially overridden values of environment variables, in conjunction with certain other plugins allowing attackers able to configure jobs to craft a build ID Token that impersonates a trusted job, potentially gaining unauthorized access to external services.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThe Jenkins OpenID Connect Provider Plugin versions 96.vee8ed882ec4d and earlier generates build ID tokens using environment variables that can be overridden by attackers with job configuration permissions. When combined with certain other plugins, this allows attackers to craft malicious build ID tokens that impersonate trusted jobs, granting unauthorized access to external services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Openid Connect ProviderApplication
<= 96.vee8ed882ec4dCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed version of the OpenID Connect Provider pluginAccess the Jenkins plugin management interface or plugin directory and locate the OpenID Connect Provider plugin to view its version numberAffected if The installed version is 96.vee8ed882ec4d or earlier (any version up to and including 96.vee8ed882ec4d)
-
Confirm the plugin is actively configuredReview Jenkins global configuration to determine if the OpenID Connect Provider plugin has been enabled and configured for useAffected if The plugin is installed and configured, enabling the vulnerable build ID token generation feature
-
Review job configurations for environment variable overridesInspect Jenkins job configurations, particularly the build environment section, for any environment variables that could influence build ID token generationAffected if Jobs contain custom environment variable definitions that could be manipulated to control build ID token values
-
Check for permissions allowing job configuration modificationsExamine Jenkins authorization matrix and job-level permissions to identify users or groups with the ability to modify job configurationsAffected if Users other than administrators have job configuration/modify permissions, allowing them to override environment variables
You are affected if the OpenID Connect Provider plugin version is 96.vee8ed882ec4d or earlier AND the plugin is configured AND jobs have environment variable overrides that attackers with job configuration permissions could exploit to manipulate build ID tokens.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the Jenkins OpenID Connect Provider Plugin to a version newer than 96.vee8ed882ec4d once available, and review job configurations for any suspicious environment variable overrides.
Fix this in Openid Connect Provider
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47884 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47884 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data