CVE-2026-9277

published 22 May 2026 · updated 14 Sep 2026

shell-quote `quote()` does not validate object-token shapes, allowing command injection via line terminators in `.op`

8.1HighCVSS 8.1EPSS 1%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in 1.8.4.

shell-quote's `quote()` function did not validate object-token inputs against the operator model used by `parse()`. The `.op` field was backslash-escaped character by character using `/(.)/g`, which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in `.op` therefore passed through unescaped into the output; POSIX shells treat a literal newline as a command separator, so any content after it would execute as a second command. The vulnerable code path is reachable in two ways: (1) direct construction of `{ op: '...\n...' }` from external input, and (2) via `parse(cmd, envFn)` when `envFn` returns object tokens whose `.op` is attacker-influenced. Both are documented API surface. Fixed by replacing the per-character escape with strict shape validation: `.op` must match the parser's control-operator allowlist; `{ op: 'glob', pattern }` validates `pattern` and forbids line terminators; `{ comment }` validates `comment` and forbids line terminators; any other object shape throws `TypeError`.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
>=1.1.0 <1.8.41.8.4

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-9277 severity on Zeptric[![CVE-2026-9277](https://zeptric.io/badge/cve/CVE-2026-9277.svg)](https://zeptric.io/cve/CVE-2026-9277)