CVE-2025-67641 Jenkins Coverage Plugin has a stored cross-site scripting (XSS) vulnerability
Attackers with Item/Configure permission can inject JavaScript via REST API, leading to stored XSS in Jenkins Coverage Plugin.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2025-67641?
CVE-2025-67641 is a high-severity cross-site scripting vulnerability in Jenkins Coverage Plugin, published on 10 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Jenkins Coverage Plugin 2.3054.ve1ff7b_a_a_123b_ and earlier does not validate the configured coverage results ID when creating coverage results, only when submitting the job configuration through the UI, allowing attackers with Item/Configure permission to use a `javascript:` scheme URL as identifier by configuring the job through the REST API, resulting in a stored cross-site scripting (XSS) vulnerability.
Weakness: CWE-79
Which versions are affected by CVE-2025-67641?
2 open source packages ship an affected version, including io.jenkins.plugins:coverage. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
io.jenkins.plugins:coverage Maven | All versions | 2.3056 |
io.jenkins.plugins:coverage Maven | All versions | 2.3056 |
Products include Jenkins Coverage.
How do I fix CVE-2025-67641?
Upgrade io.jenkins.plugins:coverage to 2.3056 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2025-67641 being exploited?
There is no known exploitation of CVE-2025-67641 in the wild and no public exploit code.
Sources
Also known as GHSA-v3f3-rf6r-43x5.