GatlingApplication · Jenkins
CVE-2025-5806
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 Gatling Plugin 136.vb_9009b_3d33a_e serves Gatling reports in a manner that bypasses the Content-Security-Policy protection introduced in Jenkins 1.641 and 1.625, resulting in a cross-site scripting (XSS) vulnerability exploitable by users able to change report content.
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 confidenceThe Jenkins Gatling Plugin version 136.vb_9009b_3d33a_e serves Gatling reports without applying the Content-Security-Policy protections that Jenkins introduced in versions 1.641 and 1.625. This CSP bypass allows injected JavaScript in report content to execute in the Jenkins UI context, creating a stored XSS vulnerability.
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
GatlingApplication
<= 136.vb_9009b_3d33a_eCVSS 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.
-
Verify Jenkins Gatling Plugin is installedNavigate to Jenkins > Manage Jenkins > Manage Plugins > Installed tab, or list files in $JENKINS_HOME/plugins/ directory looking for gatling* filesAffected if The Gatling plugin is present in the plugins directory or listed in Jenkins plugin management
-
Check the installed Gatling plugin versionIn Jenkins UI, go to Manage Jenkins > Manage Plugins > Installed and find Gatling Plugin to see its version, or inspect the plugin manifest file at $JENKINS_HOME/plugins/gatling/META-INF/MANIFEST.MFAffected if The version is 136.vb_9009b_3d33a_e or lower
-
Determine if Gatling reports have been generatedLook for Gatling report directories under Jenkins job workspaces or in $JENKINS_HOME/jobs/<job-name>/builds/<build-number>/gatling/Affected if Gatling report directories exist in any job build artifacts
-
Inspect HTTP response headers for served Gatling reportsAccess a Gatling report URL (typically /job/<job-name>/<build-number>/gatling/) and inspect the response headers for Content-Security-Policy headers, or use curl -I on the report URLAffected if The response lacks CSP headers or contains a permissive/unrestricted CSP policy for the report content
A user is affected if the Jenkins Gatling Plugin version 136.vb_9009b_3d33a_e or lower is installed AND Gatling reports are being generated and served.
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 dataUpdate to a patched version of the Jenkins Gatling Plugin once available, or remove/disable the plugin if no update is forthcoming.
Fix this in Gatling
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5806 — 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-2025-5806 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