Skip to main content
VulnerabilityPublished

CVE-2025-5806: Jenkins Gatling Plugin · Cross-site Scripting

Affects Jenkins Gatling PluginSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 45% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jun 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

To mitigate CVE-2025-5806, European organizations should: 1) Immediately identify and inventory Jenkins instances using the Gatling Plugin version 136.vb_9009b_3d33a_e. 2) Apply any available patches or updates from the Jenkins project or plugin maintainers as soon as they are released. 3) Restrict plugin usage and report upload permissions strictly to trusted users to minimize the risk of malicious report content being introduced. 4) Implement network segmentation and access controls to limit exposure of Jenkins servers to only necessary personnel and systems. 5) Enhance monitoring and logging around Jenkins activities, focusing on report uploads and user actions that could indicate exploitation attempts. 6) Educate Jenkins users about the risks of interacting with untrusted reports and encourage cautious behavior. 7) Consider temporary disabling or removing the vulnerable plugin if patching is not immediately feasible, balancing operational impact against security risk. 8) Review and strengthen Content-Security-Policy configurations at the Jenkins server level to mitigate potential bypasses. These steps go beyond generic advice by focusing on access control, monitoring, and operational adjustments tailored to the specific vulnerability context.

Description

Jenkins 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.

References

Community reviews

Loading reviews…