Findings

CVE-2026-9277

shell-quote's function did not validate object-token inputs against the operator model used by .

Published May 22, 2026 · updated Sep 14, 2026

shell-quote's function did not validate object-token inputs against the operator model used by . The field was backslash-escaped character by character using , which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in 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 from external input, and (2) via when returns object tokens whose is attacker-influenced. Both are documented API surface. Fixed by replacing the per-character escape with strict shape validation: must match the parser's control-operator allowlist; validates and forbids line terminators; validates and forbids line terminators; any other object shape throws .

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

  1. May 22, 2026 · NIST NVD

    Detected

    shell-quote's function did not validate object-token inputs against the operator model used by . The field was backslash-escaped character by character using , which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in therefore passed through unescaped into the output; POSIX shells treat a literal newline as a command separator, so any content after it woul

  2. Sep 14, 2026 · NIST NVD

    Updated

    shell-quote's function did not validate object-token inputs against the operator model used by . The field was backslash-escaped character by character using , which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line terminator in therefore passed through unescaped into the output; POSIX shells treat a literal newline as a command separator, so any content after it woul

Sources

  • CVE.orgVulnerability recordCVE-2026-9277

    Official CVE identifier

    cve.org
  • NIST NVDVulnerability recordCVE-2026-9277

    shell-quote's function did not validate object-token inputs against the operator model used by . The field was backslash-escaped character by character using , which in JavaScript does not match line terminators (\n, \r, U+2028, U+2029). A line te

    nvd.nist.gov

References