OS Command Injection in @cyclonedx/cyclonedx-npm (CVE-2026-55849)
Summary
OS command injection in @cyclonedx/cyclonedx-npm (CVE-2026-55849). Risk of unauthorized operations or information disclosure. Exploitable via npm_execpath. Mitigation: upgrade to 5.0.0 or later.
Original description
The description as published by the source.
@cyclonedx/cyclonedx-npm creates CycloneDX Software Bill of Materials from npm projects. From 2.1.0 before 5.0.0, the CLI passes user-supplied --workspace values to a subshell without proper sanitization when npm_execpath is unset or empty, allowing arbitrary OS command execution with the privileges of the invoking user. This issue is fixed in version 5.0.0.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55849 has been found in @cyclonedx/cyclonedx-npm.
Attackers can target a specific entry point like npm_execpath over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @cyclonedx/cyclonedx-npm to 5.0.0 or later.
If unsure, ask your IT team or search "@cyclonedx/cyclonedx-npm CVE-2026-55849" on the vendor's site.
CVE-2026-55849 (@cyclonedx/cyclonedx-npm) — CWE-78
Attack surface: npm_execpath
Patched: 5.0.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in @cyclonedx/cyclonedx-npm. Attackers reach the vulnerable code path via npm_execpath.
Check the vendor advisory for the affected versions of @cyclonedx/cyclonedx-npm. Attack surface: npm_execpath.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 5.0.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@cyclonedx/cyclonedx-npm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r '@cyclonedx/cyclonedx-npm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
@cyclonedx/cyclonedx-npmを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade @cyclonedx/cyclonedx-npm to 5.0.0ステージング環境で 5.0.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com