Skip to content

← Actionable
High, CVSS 8.0

Jenkins Gatling Plugin Vulnerable to Cross-Site Scripting (XSS)

CVE-2025-5806GHSA-gw97-cqwg-xmh4

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • Maven org.jenkins-ci.plugins:gatling

    Affected
    >= 136.vb, <= 136.vb
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.0 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-5806: 0.54% estimated exploitation activity in the next 30 days; percentile 45.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Jenkins Gatling Plugin 136.vb9009b3d33ae 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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-gw97-cqwg-xmh4

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-5806

Advisory: Jenkins Gatling Plugin Vulnerable to Cross-Site Scripting (XSS)
IDs: CVE-2025-5806, GHSA-gw97-cqwg-xmh4
Record: https://patchnext.com/advisories/cve-2025-5806 (revision 1, source checked 26 Oct 2026, 16:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.jenkins-ci.plugins:gatling: affected >= 136.vb, <= 136.vb

## Suggested inspection (read-only)
- Maven org.jenkins-ci.plugins:gatling: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.jenkins-ci.plugins:gatling.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gw97-cqwg-xmh4 (GitHub-reviewed advisory GHSA-gw97-cqwg-xmh4 lists affected ranges: Maven org.jenkins-ci.plugins:gatling >=136.vb <=136.vb)

Commands are suggestions: review each one before running it.

Loading voting…