Skip to main content
VulnerabilityPublished

CVE-2025-67641: Jenkins Coverage Plugin · Cross-site Scripting

Affects Jenkins Coverage PluginSource CVE Database V5

0

Not known to be exploited · CVSS 8.0 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% 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 10 Dec 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

Affected software

ProductAffectedFixed in
Jenkins Project Jenkins Coverage PluginAffected
  • =0
Fixed in–

AI-suggested

  1. Immediately audit and restrict Item/Configure permissions to only trusted users to reduce the risk of malicious configuration changes via the REST API.
  2. Monitor Jenkins REST API usage for unusual or unauthorized configuration changes, especially those involving the Coverage Plugin.
  3. Implement network segmentation and access controls to limit Jenkins server exposure to only necessary personnel and systems.
  4. Educate developers and administrators about the risks of stored XSS and the importance of secure plugin configuration.
  5. Apply security hardening best practices for Jenkins, including enabling security realms and authorization strategies that enforce least privilege.
  6. Stay alert for official patches or updates from the Jenkins project and apply them promptly once released.
  7. Consider implementing Web Application Firewall (WAF) rules to detect and block suspicious payloads targeting the Coverage Plugin endpoints.
  8. Regularly review and sanitize all user-generated inputs and configurations where possible to prevent injection attacks.

Description

CVE-2025-67641 is a high-severity stored cross-site scripting (XSS) vulnerability in the Jenkins Coverage Plugin versions 2.3054.ve1ff7b_a_a_123b_ and earlier. The flaw arises because the plugin does not properly validate the coverage results ID when configured via the REST API, allowing attackers with Item/Configure permission to inject a `javascript:` scheme URL as an identifier. This vulnerability requires authentication and user interaction but can lead to full compromise of confidentiality, integrity, and availability within the Jenkins environment. No known exploits are currently reported in the wild. The vulnerability impacts Jenkins installations using the Coverage Plugin, which is widely used in continuous integration pipelines, including in European organizations. Mitigation involves restricting Item/Configure permissions, monitoring REST API usage, and applying patches once available. Countries with significant software development sectors and Jenkins adoption, such as Germany, France, and the UK, are most likely to be affected.

References

Community reviews

Loading reviews…