# CVE-2025-64131: Jenkins SAML Plugin does not implement a replay cache

> Attackers can replay SAML authentication requests to bypass authentication and access Jenkins as another user.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 29 Oct 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-j7r7-7qmf-xq87

## What is CVE-2025-64131?

CVE-2025-64131 is a high-severity authentication bypass vulnerability in Jenkins SAML Plugin, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-294 (Authentication Bypass by Capture-replay)

## Which versions are affected by CVE-2025-64131?

2 open source packages ship an affected version, including org.jenkins-ci.plugins:saml. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:saml` | Maven | All versions | 4.583.585.v22ccc1139f55 |
| `org.jenkins-ci.plugins:saml` | Maven | All versions | 4.583.585.v22ccc1139f55 |

Products: Jenkins Saml.

## How do I fix CVE-2025-64131?

Upgrade org.jenkins-ci.plugins:saml to 4.583.585.v22ccc1139f55 or later.

## Is CVE-2025-64131 being exploited?

There is no known exploitation of CVE-2025-64131 in the wild and no public exploit code.

## Other vulnerabilities in Jenkins SAML Plugin

- [CVE-2021-21678](https://insights.sbomify.com/CVE-2021-21678/): Jenkins SAML Plugin allows bypassing CSRF protection for any URL (high 8.8)
- [CVE-2018-1000602](https://insights.sbomify.com/CVE-2018-1000602/): Jenkins SAML Plugin Session Fixation vulnerability (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-64131 and fix it if it is affected.

What it is: CVE-2025-64131 is a high-severity authentication bypass vulnerability in Jenkins SAML Plugin, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-64131 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:saml (Maven): affected all versions; fixed in 4.583.585.v22ccc1139f55
- org.jenkins-ci.plugins:saml (Maven): affected all versions; fixed in 4.583.585.v22ccc1139f55

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-64131/ (Markdown: https://insights.sbomify.com/CVE-2025-64131/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-64131
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-64131
- OSV: https://osv.dev/vulnerability/CVE-2025-64131

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-64131/
Summaries are generated and may contain mistakes; the official description above is the record.