How severe is GHSA-cjgm-9vc9-56mx?

GHSA-cjgm-9vc9-56mx has a CVSS score of 4.6/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cjgm-9vc9-56mx?

GHSA-cjgm-9vc9-56mx affects the following packages: org.jenkins-ci.plugins:matrix-project (Maven). Ecosystems affected: Maven.

How do I fix GHSA-cjgm-9vc9-56mx?

Update org.jenkins-ci.plugins:matrix-project to 822.824.v14451b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjgm-9vc9-56mx is resolved across your whole dependency graph.

How do I detect GHSA-cjgm-9vc9-56mx in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.jenkins-ci.plugins:matrix-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cjgm-9vc9-56mx 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-cjgm-9vc9-56mx?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cjgm-9vc9-56mx can be triaged on real exposure rather than presence alone.

Is GHSA-cjgm-9vc9-56mx actively exploited in the wild?

No public exploit code has been indexed for GHSA-cjgm-9vc9-56mx yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-cjgm-9vc9-56mx?

GHSA-cjgm-9vc9-56mx has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 51th 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. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-cjgm-9vc9-56mx published, and has it been updated?

GHSA-cjgm-9vc9-56mx was published on January 24, 2024 and was last updated on August 7, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

GHSA-cjgm-9vc9-56mx — matrix-project

MEDIUMFix: jenkinsci/matrix-project-plugin@f7a5b24

GHSA-cjgm-9vc9-56mx is a medium-severity (CVSS 4.6) vulnerability in org.jenkins-ci.plugins:matrix-project. A fix is available for org.jenkins-ci.plugins:matrix-project — see the affected versions and patch details below.

Path traversal vulnerability in Jenkins Matrix Project Plugin

Also known asCVE-2024-23900

Published

Jan 24, 2024

Updated

Aug 7, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-cjgm-9vc9-56mx.

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs51th percentile — riskier than 51% 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-cjgm-9vc9-56mx 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 378,156 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

1 pkg affected

☕org.jenkins-ci.plugins:matrix-project

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 Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects submitted through the config.xml REST API endpoint.

This allows attackers with Item/Configure permission to create or replace any config.xml file on the Jenkins controller file system with content not controllable by the attackers.

Matrix Project Plugin 822.824.v14451b_c0fd42 sanitizes user-defined axis names of Multi-configuration project.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.jenkins-ci.plugins:matrix-project`	all versions	822.824.v14451b`org.jenkins-ci.plugins:matrix-project:822.824.v14451b`

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.plugins:matrix-project, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.jenkins-ci.plugins:matrix-project to 822.824.v14451b or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cjgm-9vc9-56mx 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cjgm-9vc9-56mx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cjgm-9vc9-56mx. 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 HatModerate

Product	Fixed in	Advisory
OCP-Tools-4.12-RHEL-8	`jenkins-0:2.440.3.1716445200-3.el8`	RHSA-2024:3635
OCP-Tools-4.13-RHEL-8	`jenkins-0:2.440.3.1716445150-3.el8`	RHSA-2024:3636
OCP-Tools-4.14-RHEL-8	`jenkins-0:2.440.3.1716387933-3.el8`	RHSA-2024:3634
OCP-Tools-4.15-RHEL-8	`jenkins-0:2.440.3.1718879390-3.el8`	RHSA-2024:4597

Frequently Asked Questions

Jenkins Matrix Project Plugin 822.v01b_8c85d16d2 and earlier does not sanitize user-defined axis names of multi-configuration projects submitted through the `config.xml` REST API endpoint. This allows attackers with Item/Configure permission to create or replace any `config.xml` file on the Jenkins controller file system with content not controllable by the attackers. Matrix Project Plugin 822.824.v14451b_c0fd42 sanitizes user-defined axis names of Multi-configuration project.

O3 Security · Impact-Aware SCA

Is GHSA-cjgm-9vc9-56mx in your dependencies?

O3 Security finds GHSA-cjgm-9vc9-56mx across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works