CVE-2026-71538: @cyclonedx/cyclonedx-npm Shell Injection Vulnerability

HIGH
Advisory Identifier: GHSA-q69g-4hcv-6jg4
CWE-78
Published
Advisory Summary

CVE-2026-71538 is a HIGH shell injection vulnerability (CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')) affecting @cyclonedx/cyclonedx-npm libraries in the npm ecosystem. The issue involves shell injection via unsanitized --workspace argument on windows. Remediation is available by upgrading affected packages to version 6.0.0.

CVE-2026-71538 at a Glance

CVE Identifier CVE-2026-71538
GHSA Identifier GHSA-q69g-4hcv-6jg4
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Affected Product @cyclonedx/cyclonedx-npm
Package Ecosystem npm
Published Date
Last Updated

How to Fix CVE-2026-71538

To remediate this vulnerability, upgrade all affected @cyclonedx/cyclonedx-npm dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

@cyclonedx/cyclonedx-npm fixed: 6.0.0
npm install @cyclonedx/cyclonedx-npm@6.0.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls @cyclonedx/cyclonedx-npm

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-71538, inspect your project dependencies using npm:

npm ls @cyclonedx/cyclonedx-npm

Analyze the terminal output to locate any version of @cyclonedx/cyclonedx-npm in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 6.0.0), your application is affected.

Note: The npm ls @cyclonedx/cyclonedx-npm command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'), where the product constructs all or part of an os command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended os command when it is sent to a downstream component. In @cyclonedx/cyclonedx-npm, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## Summary A **Windows-specific** command injection vulnerability exists in `@cyclonedx/cyclonedx-npm` when the CLI is invoked with the `--workspace <value>` option. User-supplied `--workspace` values can be passed to a shell command without proper neutralization on the Windows fallback execution path, enabling attackers to inject arbitrary OS commands. The vulnerability was fixed in version [6.0.0][v6.0.0]. ## Vulnerability Details When `cyclonedx-npm` is executed with the `--workspace` option, the provided argument is incorporated into an internal command execution flow. On **Windows systems**, this path can interpret untrusted `--workspace` input as shell syntax if not safely handled. As a result, specially crafted workspace names can break out of the intended command context and execute arbitrary commands with the privileges of the invoking user. ## Impact An attacker who can influence the value passed to `--workspace` can execute arbitrary OS commands **on Windows hosts**. This may lead to: * Arbitrary command execution * Data exfiltration * Local privilege escalation (depending on runtime context and privileges) * Modification or destruction of files accessible to the user running the CLI The vulnerability affects only scenarios where: * The user invokes `cyclonedx-npm` with `--workspace <value>`, and * The vulnerable execution path is reached on **Windows**. ## Exploitation Conditions (High-Level) Exploitation requires the attacker to supply or influence the `--workspace` value passed to the CLI. If the tool falls back to the vulnerable shell execution path on **Windows**, specially crafted workspace identifiers can cause unintended command execution. No exploit code is included here to avoid providing weaponizable examples. ## Root Cause The CLI fallback execution path on **Windows** constructed a shell command using untrusted input from the `--workspace` option. Because the fallback code path does not sanitize or escape the workspace value, special shell metacharacters (e.g., `>`, `&`, `|`) are interpreted by the shell, enabling command injection. ## Fix The vulnerability was resolved in [PR #1489], which ensures workspace values are handled safely and are no longer passed to a vulnerable shell execution path. The fix is included in `@cyclonedx/cyclonedx-npm` version [6.0.0][v6.0.0]. ## Remediation * Upgrade to version [6.0.0][v6.0.0] or later, which contains the complete fix. * As a temporary mitigation for older versions, ensure that the environment variable `npm_execpath` is set to a `npm-cli.js` before invoking the tool. * Avoid passing untrusted or user-controlled values to the `--workspace` option. * If immediate upgrade is not possible, prioritize mitigation on **Windows systems**, where exploitability exists.

CVE-2026-71538 Affected @cyclonedx/cyclonedx-npm Versions

1 component(s)
Fixed Versions:
6.0.0
Product / Package Ecosystem Affected Versions Fixed Version
@cyclonedx/cyclonedx-npm
npm
< 6.0.0
6.0.0

References

Frequently Asked Questions

What is CVE-2026-71538?
CVE-2026-71538 is a security vulnerability in @cyclonedx/cyclonedx-npm involving Shell Injection via Unsanitized --workspace Argument on Windows under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection').
Which @cyclonedx/cyclonedx-npm versions are affected?
Affected versions include releases prior to 6.0.0 across affected packages: @cyclonedx/cyclonedx-npm.
What version fixes CVE-2026-71538?
Upgrading to 6.0.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is @cyclonedx/cyclonedx-npm affected?
Yes, @cyclonedx/cyclonedx-npm is affected in releases prior to 6.0.0. Upgrade your dependency to 6.0.0 or later.
What CWE is associated with CVE-2026-71538?
CVE-2026-71538 is classified under CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') (The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.).
How can I check npm dependencies for CVE-2026-71538?
Run the dependency tree command: 'npm ls @cyclonedx/cyclonedx-npm'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-q69g-4hcv-6jg4",
  "modified" : "2026-09-17T14:50:40Z",
  "published" : "2026-09-17T14:50:40Z",
  "aliases" : [ "CVE-2026-71538" ],
  "summary" : "@cyclonedx/cyclonedx-npm: Shell Injection via Unsanitized --workspace Argument on Windows",
  "details" : "## Summary\n\nA **Windows-specific** command injection vulnerability exists in `@cyclonedx/cyclonedx-npm` when the CLI is invoked with the `--workspace <value>` option.  \nUser-supplied `--workspace` values can be passed to a shell command without proper neutralization on the Windows fallback execution path, enabling attackers to inject arbitrary OS commands.  \n\nThe vulnerability was fixed in version [6.0.0][v6.0.0].\n\n## Vulnerability Details\n\nWhen `cyclonedx-npm` is executed with the `--workspace` option, the provided argument is incorporated into an internal command execution flow.  \nOn **Windows systems**, this path can interpret untrusted `--workspace` input as shell syntax if not safely handled.\n\nAs a result, specially crafted workspace names can break out of the intended command context and execute arbitrary commands with the privileges of the invoking user.\n\n## Impact\n\nAn attacker who can influence the value passed to `--workspace` can execute arbitrary OS commands **on Windows hosts**.  \nThis may lead to:\n\n* Arbitrary command execution\n* Data exfiltration\n* Local privilege escalation (depending on runtime context and privileges)\n* Modification or destruction of files accessible to the user running the CLI\n\nThe vulnerability affects only scenarios where:\n\n* The user invokes `cyclonedx-npm` with `--workspace <value>`, and\n* The vulnerable execution path is reached on **Windows**.\n\n## Exploitation Conditions (High-Level)\n\nExploitation requires the attacker to supply or influence the `--workspace` value passed to the CLI.  \nIf the tool falls back to the vulnerable shell execution path on **Windows**, specially crafted workspace identifiers can cause unintended command execution.  \nNo exploit code is included here to avoid providing weaponizable examples.\n\n## Root Cause\n\nThe CLI fallback execution path on **Windows** constructed a shell command using untrusted input from the `--workspace` option.  \nBecause the fallback code path does not sanitize or escape the workspace value, special shell metacharacters (e.g., `>`, `&`, `|`) are interpreted by the shell, enabling command injection.\n\n## Fix\n\nThe vulnerability was resolved in [PR #1489], which ensures workspace values are handled safely and are no longer passed to a vulnerable shell execution path.\n\nThe fix is included in `@cyclonedx/cyclonedx-npm` version [6.0.0][v6.0.0].\n\n## Remediation\n\n* Upgrade to version [6.0.0][v6.0.0] or later, which contains the complete fix.\n* As a temporary mitigation for older versions, ensure that the environment variable `npm_execpath` is set to a `npm-cli.js` before invoking the tool.\n* Avoid passing untrusted or user-controlled values to the `--workspace` option.\n* If immediate upgrade is not possible, prioritize mitigation on **Windows systems**, where exploitability exists.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "@cyclonedx/cyclonedx-npm"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "6.0.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/CycloneDX/cyclonedx-node-npm/security/advisories/GHSA-q69g-4hcv-6jg4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CycloneDX/cyclonedx-node-npm/pull/1489"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CycloneDX/cyclonedx-node-npm/commit/15d3beb5bcd2b0b6eccfdf31192f5103b3f12c0f"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/CycloneDX/cyclonedx-node-npm"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/CycloneDX/cyclonedx-node-npm/releases/tag/v6.0.0"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-78" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-09-17T14:50:40Z",
    "nvd_published_at" : null
  }
}