Jenkins Coverage Plugin
2 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Jenkins Coverage Plugin, a product in the devtools ci space. Use it to gauge the current risk picture and drill into individual advisories.
Jenkins Coverage Plugin CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 1 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 0 |
| 2026-05 | 0 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 0 |
| 2026-09 | 1 |
Severity
How the 2 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High1
- Medium1
Latest CVEs
The 2 most recently published vulnerabilities affecting Jenkins Coverage Plugin.
- CVE-2026-92135Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier does not validate the coverage results ID when a job configuration is submitted through the REST API, allowing attackers with Item/Configure...8.0
- CVE-2025-67641Jenkins 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 ...5.4
Product grouping is registry-driven, with AI assist and human review. How it works