Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven
Not in CISA KEV
HIGH severity

GHSA-864v-5q2g-fr64 jenkins-core

HIGHFix: jenkinsci/jenkins@e7443ef

GHSA-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.

Stored XSS vulnerability in Jenkins 'keep forever' badge icon

Also known asBIT-jenkins-2020-2222CVE-2020-2222
Published
May 24, 2022
Updated
Feb 16, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Sep 19, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.1%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs65th percentile — riskier than 65% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-864v-5q2g-fr64 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,166 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

2 pkgs affected
org.jenkins-ci.main:jenkins-coreorg.jenkins-ci.main:jenkins-core

Real-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

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.jenkins-ci.main:jenkins-coreall versions2.235.2org.jenkins-ci.main:jenkins-core:2.235.2
Mavenorg.jenkins-ci.main:jenkins-core2.236&&< 2.2452.245org.jenkins-ci.main:jenkins-core:2.245

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-864v-5q2g-fr64 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-864v-5q2g-fr64. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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.

Red HatImportant
ProductFixed inAdvisory
Red Hat OpenShift Container Platform 3.11jenkins-0:2.235.2.1597220898-1.el7RHSA-2020:3541
Red Hat OpenShift Container Platform 4.3jenkins-0:2.235.5.1600415514-1.el7RHSA-2020:3808
Red Hat OpenShift Container Platform 4.4jenkins-0:2.235.2.1597312065-1.el7RHBA-2020:3441
Red Hat OpenShift Container Platform 4.4openshift-0:4.4.0-202008250319.p0.git.0.d653415.el7RHSA-2020:3579
Red Hat OpenShift Container Platform 4.5jenkins-0:2.235.2.1597312414-1.el7RHSA-2020:3519

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is GHSA-864v-5q2g-fr64 in your dependencies?

O3 Security finds GHSA-864v-5q2g-fr64 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-864v-5q2g-fr64: jenkins-core (High 8) | O3 Security