Stored XSS via unvalidated coverage results identifier
Published Sep 16, 2026 · Updated Sep 16, 2026
Stored XSS in Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier allows remote authenticated users to execute script in Jenkins pages. The REST job-configuration path accepts a coverage results ID using the javascript: scheme, then uses that identifier as a UI link without validation. Exploitation requires Item/Configure permission and a user to follow the stored link, allowing script execution in that user's Jenkins browser context.
Summary
What happened
Stored XSS in Jenkins Coverage Plugin 3.3358.v9487dde48783 and earlier allows remote authenticated users to execute script in Jenkins pages. The REST job-configuration path accepts a coverage results ID using the javascript: scheme, then uses that identifier as a UI link without validation. Exploitation requires Item/Configure permission and a user to follow the stored link, allowing script execution in that user's Jenkins browser context.
The record
- CVE
- CVE-2026-92135
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- Jenkins Project
- Product
- Jenkins Coverage Plugin
- Classifications
- T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo