← Back to the live CVE advisory feed

CVE-2026-102422: shell-quote

Severity

9.2 (CRITICAL)

Affected versions

1.8.4 through before 1.11.0

Fixed version

1.11.0

Patch status

Patched

Published

2026-09-29T04:17:55.707

Modified

2026-09-29T04:17:55.707

Why it matters

This matters because the issue affects identity or token handling. Successful exploitation could allow unauthorized authentication, client manipulation, or access to protected services.

Recommended admin actions

• Prioritize validation immediately due to critical CVSS severity.

Technical summary

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.

View the official NVD record for CVE-2026-102422

CVE data is sourced from NVD/CNA records and optional enrichment. Validate against the vendor advisory before taking production action.