Html PublisherApplication · Jenkins
CVE-2026-42524
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 · uneditedJenkins HTML Publisher Plugin 427 and earlier does not escape job name and URL in the legacy wrapper file, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Item/Configure permission.
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 confidenceJenkins HTML Publisher Plugin versions 427 and earlier fails to properly escape job names and URLs when generating legacy wrapper files, allowing stored XSS injection. Attackers with Item/Configure permission can inject malicious scripts into job configuration that execute when users view the HTML reports.
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
<= 427CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check HTML Publisher Plugin versionNavigate to Manage Jenkins > Manage Plugins > Installed tab, locate 'HTML Publisher' plugin, and note the version number displayedAffected if The version is 427 or earlier (e.g., 427.v1a_7f4a_7e5b_9c, 426.v5f0b_8b_5c_8a_8)
-
Identify jobs using HTML Publisher reportsReview Jenkins job configurations: for each job, go to Configure > Post-build Actions > Publish HTML reports, and check if any HTML report publishing is configuredAffected if Any job is configured with HTML Publisher reports (the report generation creates the vulnerable wrapper files)
-
Locate generated HTML wrapper filesOn the Jenkins controller, navigate to the job's build directory (typically $JENKINS_HOME/jobs/<jobname>/builds/<buildnumber>/htmlreports/) and locate the HTML files generated by the pluginAffected if Legacy wrapper HTML files exist in the build directory - these are the files where unsanitized job names/URLs are written
-
Inspect wrapper file source for unsanitized inputOpen one of the generated HTML files in a text editor and examine the content for job name or URL values - look for unescaped characters like <, >, ", or ' appearing within HTML attributes or textAffected if The HTML file contains raw job name or URL strings that are not HTML-encoded (e.g., <script> tags present in what should be escaped content)
You are affected if HTML Publisher Plugin version is 427 or earlier AND jobs are configured to publish HTML reports that generate wrapper files with unsanitized job names or URLs.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade Jenkins HTML Publisher Plugin to version 428 or later which includes proper output encoding for job names and URLs in legacy wrapper files.
Fix this in Html Publisher
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42524 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42524 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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