Cross-Site Scripting (XSS) in Jenkins Coverage Plugin (CVE-2026-92135)
Summary
Cross-site scripting in Jenkins Coverage Plugin (CVE-2026-92135). Successful exploitation can lead to full system takeover.
Original description
The description as published by the source.
Jenkins 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 permission to use a javascript: scheme URL as identifier, resulting in a stored cross-site scripting (XSS) vulnerability.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-92135 has been found in Jenkins Coverage Plugin.
Successful exploitation can lead to full system takeover. CVSS score: 8.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Jenkins Coverage Plugin CVE-2026-92135" on the vendor's site.
CVE-2026-92135 (Jenkins Coverage Plugin) — CWE-79 / CVSS v3 8.0
Attack vector: remote (network-reachable)
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in Jenkins Coverage Plugin.
Check the vendor advisory for the affected versions of Jenkins Coverage Plugin.
Severity: High (CVSS 8.0/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Jenkins Coverage Plugin を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web jenkins.io
- web nvd.nist.gov
- web github.com