dbcve.org
JdependApplication · Jenkins

CVE-2025-64134

HIGH · 7.1 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to after 1.3.1 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

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 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.

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 confidence

The Jenkins JDepend Plugin versions 1.3.1 and earlier include an outdated JDepend Maven Plugin component that fails to configure its XML parser securely, allowing XML External Entity (XXE) attacks. An attacker could craft malicious XML files processed by the plugin to read internal files or cause denial of service.

MitigationUpdate Jenkins JDepend Plugin to a version where the JDepend Maven Plugin includes proper XXE protection in its XML parser configuration.

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
JdependApplication
Affected:<= 1.3.1

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

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

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. Identify JDepend Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, then search for 'JDepend' or 'jdepend' in the plugin list. The version will be displayed in the 'Version' column.
    Affected if The displayed version is 1.3.1 or any version lower than 1.3.1
  2. Confirm plugin is in use
    Check your Jenkins jobs (freestyle or pipeline) for the 'Invoke JDepend analysis' build step or any build step that uses the JDepend plugin to analyze Java code metrics.
    Affected if The JDepend build step is configured in any of your Jenkins jobs and the plugin version is <= 1.3.1
  3. Check for XML file processing
    Review the JDepend configuration in your jobs. Look at the 'targets' or 'files' parameter in the JDepend build step to identify which XML or Java package files are being analyzed.
    Affected if The JDepend plugin processes XML files (such as package.xml or other JDepend-related XML reports) and the plugin version is <= 1.3.1

You are affected if the Jenkins JDepend Plugin version is 1.3.1 or earlier AND your Jenkins jobs use the JDepend build step to process XML files.

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.

From vendor data
Upgrade available Upgrade to a release after 1.3.1
Interim mitigation

Update Jenkins JDepend Plugin to a version where the JDepend Maven Plugin includes proper XXE protection in its XML parser configuration.

Fix this in Jdepend Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64134 — 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-64134 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