dbcve.org
SamlApplication · Jenkins

CVE-2025-64131

HIGH · 7.5 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to 4.583.585.v22ccc1139f55 or later.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Jenkins SAML Plugin 4.583.vc68232f7018a_ and earlier does not implement a replay cache, allowing attackers able to obtain information about the SAML authentication flow between a user's web browser and Jenkins to replay those requests, authenticating to Jenkins as that user.

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 · high confidence

Jenkins SAML Plugin versions 4.583.vc68232f7018a_ and earlier lack a replay cache mechanism. An attacker who can intercept or observe the SAML authentication flow between a user's browser and Jenkins can capture and replay authentication requests, allowing them to hijack the user's session and authenticate as that victim user.

MitigationUpgrade Jenkins SAML Plugin to the latest version which implements a replay cache. Until then, monitor for suspicious authentication patterns and limit exposure of SAML authentication traffic to trusted networks.

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
SamlApplication
Affected:< 4.583.585.v22ccc1139f55

CVSS 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
High
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Jenkins SAML Plugin is installed
    Navigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or check the plugin manifest file in the Jenkins plugins directory
    Affected if The Jenkins SAML Plugin appears in the installed plugins list
  2. Determine the installed SAML Plugin version
    In Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed tab and locate the SAML Plugin entry to view its version number
    Affected if The installed version is 4.583.vc68232f7018a_ or earlier, or any version below 4.583.585.v22ccc1139f55
  3. Confirm SAML authentication is configured and active
    Navigate to Manage Jenkins > Security > Security Realm and verify SAML is selected as the authentication method
    Affected if SAML authentication is enabled as the Security Realm - the replay attack vulnerability only applies when SAML is actively used for user authentication
  4. Check for any custom network-level replay protection
    Review network infrastructure (load balancers, proxies, WAF) between users and Jenkins for SAML replay mitigation settings
    Affected if No replay protection exists at the network layer and the plugin version is within the affected range

A user is affected if the Jenkins SAML Plugin version is below 4.583.585.v22ccc1139f55 AND SAML authentication is actively configured as the Security Realm in Jenkins.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to 4.583.585.v22ccc1139f55 or later
Fixed in 4.583.585.v22ccc1139f55
Interim mitigation

Upgrade Jenkins SAML Plugin to the latest version which implements a replay cache. Until then, monitor for suspicious authentication patterns and limit exposure of SAML authentication traffic to trusted networks.

Recommended fix High confidence

4.583.585.v22ccc1139f55

  1. Check current Jenkins SAML Plugin version in Manage Jenkins > Manage Plugins > Installed
  2. Upgrade Jenkins SAML Plugin to version 4.583.585.v22ccc1139f55 or later through the plugin manager
  3. Restart Jenkins if required to complete the upgrade
  4. Verify the upgraded plugin version is showing correctly
  5. Test SAML single sign-on authentication to confirm functionality works

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Saml Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64131 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64131 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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