# CVE-2025-64134: Jenkins JDepend Plugin vulnerable to XML external entity attacks

> An attacker can exploit an outdated XML parser in the Jenkins JDepend Plugin to perform XML External Entity attacks, potentially reading sensitive files or causing denial of service.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-jfg6-4gx3-3v7w

## What is CVE-2025-64134?

CVE-2025-64134 is a high-severity vulnerability in Jenkins JDepend Plugin, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Jenkins JDepend Plugin 1.3.1 and earlier includes an outdated version of JDepend Maven Plugin that does not configure its XML parser to prevent XML external entity (XXE) attacks.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jenkins-ci.plugins:jdepend` | Maven | All versions to 1.3.1 | None |
| `org.jenkins-ci.plugins:jdepend` | Maven | All versions to 1.3.1 | None |

Products: Jenkins Jdepend.

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

No fix has been published for CVE-2025-64134 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-64134 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64134 is a high-severity vulnerability in Jenkins JDepend Plugin, published on 29 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-64134 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.jenkins-ci.plugins:jdepend (Maven): affected all versions up to 1.3.1; no fix listed
- org.jenkins-ci.plugins:jdepend (Maven): affected all versions up to 1.3.1; no fix listed

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-64134/ (Markdown: https://insights.sbomify.com/CVE-2025-64134/index.md)
```

## Sources

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

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