CycloneDX cdxgen may execute code contained within build-related filesGHSA-hxf3-vgpm-fv9p
MEDIUMFix: CycloneDX/cdxgen#1614GHSA-hxf3-vgpm-fv9p is a medium-severity (CVSS 6.4) Code Injection vulnerability in @cyclonedx/cdxgen. A fix is available for @cyclonedx/cdxgen — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-hxf3-vgpm-fv9p.
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
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@cyclonedx/cdxgennpmDescription
CycloneDX cdxgen prior to 11.1.7, when run against an untrusted codebase, may execute code contained within build-related files such as build.gradle.kts, a similar issue to CVE-2022-24441. cdxgen is used by, for example, OWASP dep-scan. NOTE: this has been characterized as a design limitation, rather than an implementation mistake.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @cyclonedx/cdxgen | all versions | 11.1.7npm install @cyclonedx/cdxgen@11.1.7 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @cyclonedx/cdxgen, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @cyclonedx/cdxgen to 11.1.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hxf3-vgpm-fv9p is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.
Frequently Asked Questions
Is GHSA-hxf3-vgpm-fv9p in your dependencies?
Find it across npm, including transitive dependencies.