CVE-2025-67641: Jenkins Coverage Plugin Stored XSS Vulnerability
Summary
CVE-2025-67641: Jenkins Coverage Plugin has a stored cross-site scripting (XSS) vulnerability. Affects io.jenkins.plugins:coverage versions < 2.3056. Fixed in 2.3056. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The Jenkins Coverage Plugin is an essential tool used in Jenkins CI/CD pipelines to provide coverage reports for code analysis. It allows developers to visualize how much of their code is tested, helping to improve code quality. However, this plugin has a vulnerability that can be exploited if proper security measures are not in place.
Vulnerability Detail
The Jenkins Coverage Plugin versions 2.3054.ve1ff7b_a_a_123b_ and earlier are susceptible to a stored cross-site scripting (XSS) vulnerability. This issue arises because the plugin does not validate the configured coverage results ID when creating coverage results. Attackers with Item/Configure permission can exploit this by using a 'javascript:' scheme URL as an identifier through the REST API, leading to potential malicious script execution in the context of other users.
How To Fix
Latest published version: 3.3497.v3fee733ca_b_35 as of 23 Oct 2026
Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
2.3056
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, restrict access to the Item/Configure permission for users who do not need it, thereby minimizing the risk of exploitation until the plugin is updated.
Conclusion
The Jenkins Coverage Plugin has a critical stored XSS vulnerability that can be exploited by attackers with specific permissions. It is crucial to update to the patched version to mitigate risks. Additionally, utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for io.jenkins.plugins:coverage →
FAQ
The CVSS score of this vulnerability is 8.0, indicating a high severity level.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If exploited, this vulnerability can allow attackers to execute arbitrary JavaScript in the context of other users, potentially leading to data theft or session hijacking.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just the pom.xml file.
If immediate updates are not possible, consider restricting access to sensitive permissions and monitoring your application for unusual activities.
