How severe is GHSA-9g4m-ffx6-c29g?

GHSA-9g4m-ffx6-c29g has a CVSS score of 8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-9g4m-ffx6-c29g?

GHSA-9g4m-ffx6-c29g affects the following packages: org.jenkins-ci.main:jenkins-core (Maven), org.jenkins-ci.main:jenkins-core (Maven). Ecosystems affected: Maven.

How do I fix GHSA-9g4m-ffx6-c29g?

Update org.jenkins-ci.main:jenkins-core to 2.235.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g4m-ffx6-c29g is resolved across your whole dependency graph.

How do I detect GHSA-9g4m-ffx6-c29g in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-9g4m-ffx6-c29g if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-9g4m-ffx6-c29g?

O3 pinpoints whether GHSA-9g4m-ffx6-c29g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-9g4m-ffx6-c29g actively exploited in the wild?

Yes. There are 2 known exploit references for GHSA-9g4m-ffx6-c29g, including 1 documented proof-of-concept exploit on Exploit-DB and 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-9g4m-ffx6-c29g?

GHSA-9g4m-ffx6-c29g has an EPSS (Exploit Prediction Scoring System) score of 83.1%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is GHSA-9g4m-ffx6-c29g?

GHSA-9g4m-ffx6-c29g is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-9g4m-ffx6-c29g published, and has it been updated?

GHSA-9g4m-ffx6-c29g was published on May 24, 2022 and was last updated on February 16, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-9g4m-ffx6-c29g: jenkins-core Cross-Site Scripting (High 8)

EPSS Exploitation Probability

via FIRST.org ↗

83.1%probability of exploitation in next 30 days

Very High Risk100th percentile+81.77%

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.

Blast Radius

2 pkgs affected

☕org.jenkins-ci.main:jenkins-core☕org.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.251 and earlier, LTS 2.235.3 and earlier does not escape the project naming strategy description, that is displayed on item creation.\n\nThis results in a stored cross-site scripting (XSS) vulnerability exploitable by users with Overall/Manage permission.\n\nJenkins 2.252, LTS 2.235.4 escapes the project naming strategy description.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.main:jenkins-core`	all versions	2.235.4
☕Maven	`org.jenkins-ci.main:jenkins-core`	≥ 2.236&&< 2.252	2.252

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.main:jenkins-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.jenkins-ci.main:jenkins-core to 2.235.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9g4m-ffx6-c29g is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-9g4m-ffx6-c29g is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-9g4m-ffx6-c29g. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Jenkins 2.251 and earlier, LTS 2.235.3 and earlier does not escape the project naming strategy description, that is displayed on item creation.\n\nThis results in a stored cross-site scripting (XSS) vulnerability exploitable by users with Overall/Manage permission.\n\nJenkins 2.252, LTS 2.235.4 escapes the project naming strategy description.

O3 Security · Impact-Aware SCA

Is GHSA-9g4m-ffx6-c29g in your dependencies?

O3 detects GHSA-9g4m-ffx6-c29g across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-9g4m-ffx6-c29g