dbcve.org
Html PublisherApplication · Jenkins

CVE-2025-53651

MEDIUM · 6.3 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 427 or later.
See remediation →
69/100
Remediation priority · Elevated
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 HTML Publisher Plugin 425 and earlier displays log messages that include the absolute paths of files archived during the Publish HTML reports post-build step, exposing information about the Jenkins controller file system in the build log.

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 HTML Publisher Plugin versions 425 and earlier inadvertently logs absolute file system paths of archived HTML reports during the Publish HTML reports post-build action, exposing the internal directory structure of the Jenkins controller in build console output.

MitigationUpdate to a patched version of the HTML Publisher Plugin when available, and limit access to build logs to authenticated, authorized users to reduce exposure of this information disclosure.

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
Html PublisherApplication
Affected:< 427

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
Low
Integrity
Low
Availability
Low

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

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. Check HTML Publisher Plugin version
    Navigate to Manage Jenkins > Manage Plugins > Installed tab, search for 'HTML Publisher' and note the version number
    Affected if The installed version is 425 or earlier (versions prior to 427)
  2. Identify jobs using HTML Publisher
    Search for jobs with 'Publish HTML reports' post-build action configured. Use Jenkins script console with: Jenkins.instance.allItems.each { job -> if (job.hasProperty('publishers')) { job.publishers.each { p -> if (p.class.name.contains('HtmlPublisher')) { println job.fullName } } } }
    Affected if The plugin is installed and configured on any job
  3. Examine build console output for path leakage
    Review recent build console logs for jobs using HTML Publisher. Look for lines containing '/var/jenkins_home/workspace/', 'C:\Jenkins\workspace\', or similar absolute paths that reveal the Jenkins controller file system
    Affected if Build console output contains absolute file paths ending with report directories like 'htmlreports/' or similar HTML report folders
  4. Inspect archived HTML report directories
    Navigate to the build artifacts directory (typically in JENKINS_HOME/jobs/JOBNAME/builds/NUMBER/archive/) and check if the directory structure is visible or referenced in logs
    Affected if Absolute paths to archived report directories appear in any build log

A user is affected if the HTML Publisher Plugin version is 425 or earlier AND build console output from jobs using this plugin reveals absolute file system paths.

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 427 or later
Fixed in 427
Interim mitigation

Update to a patched version of the HTML Publisher Plugin when available, and limit access to build logs to authenticated, authorized users to reduce exposure of this information disclosure.

Recommended fix High confidence

Html Publisher Plugin 427

  1. 1. Log in to the Jenkins controller as an administrator
  2. 2. Navigate to 'Manage Jenkins' > 'Manage Plugins'
  3. 3. Go to the 'Installed' tab
  4. 4. Locate the 'HTML Publisher Plugin' in the list
  5. 5. If an update is available, click 'Update now' to update to the latest version which includes version 427 or later
  6. 6. Alternatively, navigate to 'Advanced' > 'Upload Plugin' and upload the specific .hpi file for version 427 if available
  7. 7. After installation/update, restart the Jenkins controller (or wait for the next safe restart) to apply the changes
  8. 8. Verify the fix by running a build that uses the Publish HTML reports post-build action and confirming that absolute file paths no longer appear in the build log

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

Fix this in Html Publisher 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-53651 — 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-53651 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