Stored XSS vulnerability in Jenkins 'keep forever' badge iconGHSA-864v-5q2g-fr64
HIGHFix: jenkinsci/jenkins@e7443efGHSA-864v-5q2g-fr64 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.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
org.jenkins-ci.main:jenkins-core☕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.244 and earlier, LTS 2.235.1 and earlier does not escape the job name in the 'Keep this build forever' badge tooltip. This results in a stored cross-site scripting (XSS) vulnerability exploitable by users able to configure job names.
As job names do not generally support the character set needed for XSS, this is believed to be difficult to exploit in common configurations.
Jenkins 2.245, LTS 2.235.2 escapes the job name in the 'Keep this build forever' badge tooltip.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.jenkins-ci.main:jenkins-core | all versions | 2.235.2org.jenkins-ci.main:jenkins-core:2.235.2 |
| ☕Maven | org.jenkins-ci.main:jenkins-core | ≥ 2.236&&< 2.245 | 2.245org.jenkins-ci.main:jenkins-core:2.245 |
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.235.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-864v-5q2g-fr64 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.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat OpenShift Container Platform 3.11 | jenkins-0:2.235.2.1597220898-1.el7 | RHSA-2020:3541 |
| Red Hat OpenShift Container Platform 4.3 | jenkins-0:2.235.5.1600415514-1.el7 | RHSA-2020:3808 |
| Red Hat OpenShift Container Platform 4.4 | jenkins-0:2.235.2.1597312065-1.el7 | RHBA-2020:3441 |
| Red Hat OpenShift Container Platform 4.4 | openshift-0:4.4.0-202008250319.p0.git.0.d653415.el7 | RHSA-2020:3579 |
| Red Hat OpenShift Container Platform 4.5 | jenkins-0:2.235.2.1597312414-1.el7 | RHSA-2020:3519 |
| Red Hat OpenShift Container Platform 4.6 | openshift4/ose-aws-ebs-csi-driver-rhel8:v4.6.0-202010061132.p0 | RHBA-2020:4196 |
Frequently Asked Questions
Is GHSA-864v-5q2g-fr64 in your dependencies?
Find it across Maven, including transitive dependencies.