CVE-2026-102422
Published:September 29, 2026
Updated:October 09, 2026
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.
Affected Packages
https://github.com/ljharb/shell-quote.git (GITHUB):
Affected version(s) >=v1.8.4 <v1.11.0Fix Suggestion:
Update to version v1.11.0shell-quote (NPM):
Affected version(s) >=1.8.4 <1.11.0Fix Suggestion:
Update to version 1.11.0Related Resources (6)
Do you need more information?
Contact UsCVSS v4
Base Score:
9.2
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
PRESENT
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
HIGH
Vulnerable System Availability
HIGH
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
8.1
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Weakness Type (CWE)
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
EPSS
Base Score:
0.38