GPU VulnDB

Database/Control plane, storage & DevOps

Jenkins HTML Publisher Plugin: job name and URL unescaped in the legacy wrapper, giving stored XSS

CVSS 8.0CVE-2026-42524Control plane, storage & DevOpscurated

Impact

Versions 427 and earlier do not escape the job name or URL written into the legacy wrapper file, so a user who can configure a job stores script that runs in the browser of anyone who later views the published report. On a build controller that deploys to a GPU fleet, the viewer is usually an administrator, and script in their session can reach the Jenkins API with their rights - credentials, job definitions, and the pipelines that push images and drivers to nodes. The exposure is bounded by who already holds Item/Configure: this is a privilege escalation path inside the controller, not an unauthenticated entry point.

Who can reach it

An authenticated Jenkins user holding Item/Configure permission. A second user must then open the published HTML report for the payload to fire.

What to do

Update the HTML Publisher Plugin past 427 per the Jenkins security advisory and restart the controller; the advisory is the authority on the fixed version, which the record does not state. If an update has to wait, tighten Item/Configure membership and treat existing published reports from untrusted job authors as suspect. Nothing on the GPU nodes themselves changes.

References

Related entries

All Control plane, storage & DevOps entries

This entry is curated: imported from vendor advisories with machine assistance, not yet individually verified. Confirm against your vendor's advisory before acting, and report anything wrong.