Is CVE-2026-92135 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-92135 being exploited in the wild.

How severe is CVE-2026-92135?

High severity, with a CVSS score of 8, published 16 September 2026.

Which products and versions are affected?

Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier.

Is there a fix for CVE-2026-92135?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-92135 attacked?

It is attacked over the network.

Am I affected by CVE-2026-92135?

Check whether you run Jenkins Coverage Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-92135: Jenkins Coverage Plugin stored XSS via coverage results ID validation bypass

CVE-2026-92135 · Severity: high · CVSS 8 · Published 2026-09-16

Jenkins Coverage Plugin is a widely-used plugin for collecting and reporting code coverage metrics in CI/CD pipelines. Attackers with job configuration permissions can inject malicious JavaScript code through an unvalidated coverage results identifier field in the REST API, which executes in the browsers of anyone viewing the affected job configuration. This allows credential theft, session hijacking, or actions performed on behalf of authenticated Jenkins users.

Vendors: Jenkins.

Quick answers

Is CVE-2026-92135 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-92135 being exploited in the wild.
How severe is CVE-2026-92135?: High severity, with a CVSS score of 8, published 16 September 2026.
Which products and versions are affected?: Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier.
Is there a fix for CVE-2026-92135?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-92135 attacked?: It is attacked over the network.
Am I affected by CVE-2026-92135?: Check whether you run Jenkins Coverage Plugin at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The Coverage Plugin version 3.3358.v9487dde48783 and earlier fails to validate the coverage results ID parameter when job configurations are submitted via the REST API. An attacker with Item/Configure permission can supply a javascript: scheme URL as the identifier value, which is stored without sanitization. When the job configuration is viewed, the malicious URL executes in the context of the viewer's browser session, enabling stored cross-site scripting (XSS). The vulnerability requires Item/Configure permission to exploit but affects all users who subsequently view the affected job. A patch is available in Jenkins Coverage Plugin versions after 3.3358.v9487dde48783.

Affected products

Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier

Timeline

2026-09-16: disclosed

References

https://www.jenkins.io/security/advisory/2026-09-16/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.