CVE-2025-67641 is a stored cross-site scripting vulnerability in Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier. The plugin validates the configured coverage results identifier when job configuration is submitted through the web UI, but does not apply equivalent validation when coverage results are created through the REST API. An attacker with Item/Configure permission can therefore supply a coverage results ID using a javascript: scheme and persist malicious script-bearing data in job configuration or generated coverage report metadata. When the affected identifier is later rendered in the Jenkins web interface, the injected script can execute in the victim’s browser context. The issue was fixed in Coverage Plugin 2.3056.v1dfe888b_0249 by enforcing stricter validation of result identifiers.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A high-severity stored XSS vulnerability in Jenkins Coverage Plugin allowing attackers with configuration permissions to inject malicious scripts into coverage reports.
A stored cross-site scripting (XSS) vulnerability in Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier allows attackers with Item/Configure permission to inject malicious JavaScript via the REST API by using a crafted coverage results ID, due to insufficient validation.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.