CVE-2025-64134VulnerabilityPublished 29 Oct 2025Updated 4 Nov 2025

CVE-2025-64134: Jenkins JDepend Plugin · XML External Entity (XXE)

Affects Jenkins JDepend PluginSource CVE Database V5

Not known to be exploited · CVSS 7.1 High.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

7.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 28% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: Low
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 29 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Mavenorg.jenkins-ci.plugins/jdepend`pkg:maven/org.jenkins-ci.plugins/jdepend`Other threats	Affected <=1.3.1	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor Jenkins plugin repositories and official Jenkins security advisories for an official patch or updated version of the JDepend Plugin that addresses the XXE vulnerability, and apply it promptly once available. 2. Until a patch is released, restrict access to Jenkins instances and the JDepend Plugin functionality to trusted users only, minimizing the risk of exploitation by unauthorized or low-privileged users. 3. Implement network segmentation and firewall rules to limit Jenkins server exposure, especially restricting inbound access to trusted IP ranges. 4. Configure Jenkins security settings to enforce strong authentication and role-based access control (RBAC), ensuring that only necessary users have permissions to execute or configure the JDepend Plugin. 5. Where possible, disable or remove the JDepend Plugin if it is not essential to the build process, reducing the attack surface. 6. Employ XML parser hardening techniques by customizing plugin or Jenkins configuration to disable external entity processing if supported. 7. Conduct regular security audits and scanning of Jenkins environments to detect any anomalous activity or attempts to exploit XXE vulnerabilities. 8. Educate development and DevOps teams about the risks of XXE and the importance of secure plugin management.

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.

Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality of sensitive build and configuration data within Jenkins environments. Since Jenkins is widely adopted across Europe for software development and DevOps automation, exploitation could lead to exposure of proprietary source code, credentials, or internal network information. This could facilitate further lateral movement or targeted attacks against intellectual property or critical infrastructure. The requirement for low privileges means that even compromised or less-privileged users could leverage this flaw to escalate information disclosure. The impact is especially critical for sectors with strict data protection regulations such as finance, healthcare, and government, where leakage of sensitive data could result in regulatory penalties and reputational damage. Additionally, the vulnerability could undermine trust in automated build pipelines, potentially disrupting software delivery processes. The absence of known exploits in the wild provides a window for proactive defense, but the high CVSS score indicates that the threat should be treated with urgency.

CWE-611Improper Restriction of XML External Entity Reference (opens in a new tab)
Base weaknessOWASP Top 10 A02:2025: Security Misconfiguration (opens in a new tab)
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
Implementation · System Configuration
Many XML parsers and validators can be configured to disable external entity expansion.
OWASP Cheat Sheets
Deserialization (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V5.5.2 (opens in a new tab)
Attack patterns
Data Serialization External Entities Blowup (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Nov 2025, 15:52 UTC

WeaknessesCWE-611

Technical details

References

Community reviews

Related threats