Jenkins: Stored XSS vulnerability in node offline cause descriptionGHSA-93qh-vwrm-c5pw
HIGHFix: jenkinsci/jenkins@20041e8GHSA-93qh-vwrm-c5pw is a high-severity (CVSS 8) Cross-site Scripting (XSS) vulnerability in org.jenkins-ci.main:jenkins-core. A fix is available for org.jenkins-ci.main:jenkins-core — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-93qh-vwrm-c5pw.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-93qh-vwrm-c5pw by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 394,803 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.jenkins-ci.main:jenkins-coreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Jenkins 2.483 through 2.567 (both inclusive), LTS 2.492.1 through 2.555.2 (both inclusive) does not escape the user-provided description of a generic offline cause that could be set through the POST config.xml API, resulting in a stored cross-site scripting (XSS) vulnerability exploitable by attackers with Agent/Configure permission.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.483&&< 2.568 | 2.568org.jenkins-ci.main:jenkins-core:2.568 |
Affected Products
jenkinsjenkinsDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.568 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-93qh-vwrm-c5pw is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
To fully mitigate this vulnerability, upgrade the Jenkins instance to version 2.568 or LTS 2.555.3 (or later). These releases officially resolve the issue by securely rendering the offline cause descriptions as plain text. If an immediate upgrade is not feasible, the risk can be significantly reduced by auditing Role-Based Access Control (RBAC) settings and strictly limiting the Agent/Configure permission to highly trusted, essential administrators only.Source: Red Hat security advisory for GHSA-93qh-vwrm-c5pw (CC BY 4.0)
Frequently Asked Questions
Is GHSA-93qh-vwrm-c5pw in your dependencies?
Find it across Maven, including transitive dependencies.