CVE-2026-102422 (High) detected in shell-quote-1.9.0.tgz - autoclosed #12841

Vulnerable Library - shell-quote-1.9.0.tgz

quote and parse shell commands

Library home page: https://registry.npmjs.org/shell-quote/-/shell-quote-1.9.0.tgz

Sample Path to Dependency File: /package.json

Path to vulnerable library: /package.json

Dependency Hierarchy:

• rspack-plugin-1.5.16.tgz (Root Library)
  • sdk-1.5.16.tgz
    • launch-editor-2.14.1.tgz
      • ❌ shell-quote-1.9.0.tgz (Vulnerable Library)

Found in HEAD commit: 4f2a7131d9cdb72c0b6ec2df38bf840af14e67bb

Found in base branch: main

Vulnerability Details

shell-quote's "quote()" function emits a "{ comment }" token as "#" followed by its text, which comments out the rest of the shell line, including the opening quote of any later string token. A line terminator (\n, \r, U+2028, U+2029) in that later string therefore ends the comment, and the rest of the string is parsed as shell input: "quote(['echo', 'ok', { comment: 'x' }, 'a\nid;#'])" runs "id" in sh, bash, dash, ksh and zsh. "parse()" emits a comment token for a "#" in the middle of a word (for example "http://example.com/#frag"), so callers that combine "parse()" output with another untrusted string, such as "quote(parse(untrustedCommand).concat(untrustedArg))", are affected. The fix for CVE-2026-9277 rejected line terminators in the comment's own text, but not in the tokens after it. Fixed in 1.11.0: "quote()" throws a "TypeError" when a string after a "{ comment }" token contains a line terminator.

Publish Date: 2026-09-29

URL: CVE-2026-102422

CVSS 3 Score Details (8.1)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: High
  • Privileges Required: None
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

Suggested Fix

Type: Upgrade version

Release Date: 2026-09-29

Fix Resolution: shell-quote - 1.11.0