---
title: "GHSA-pqg4-j6r4-53mv: shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token"
description: "Critical severity. shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token. Affects shell-quote; fixed in 1.11.0."
url: https://inlinr.com/advisories/GHSA-pqg4-j6r4-53mv
lang: en
---

[Packages](https://inlinr.com/packages) / [shell-quote](https://inlinr.com/packages/shell-quote) / [Security](https://inlinr.com/packages/shell-quote/security)

Critical Vulnerability GHSA-pqg4-j6r4-53mv CVE-2026-102422 Published 6 Oct 2026

# shell-quote: \`quote()\` command injection via a line terminator in a token after a \`{ comment }\` token

Your version 

Affected releases · [shell-quote](https://inlinr.com/packages/shell-quote)

- 1.x 1.8.4 – 1.10.0 Fixed in 1.11.0

On 1.x, the newest line:

```
npm install shell-quote@1.11.0
```

Every release on a timeline

1. Not affected

0.0.0 – 1.8.3  
29 releases
2. Affected

1.8.4 – 1.10.0  
3 releases
3. Fixed

1.11.0 – 1.12.0  
2 releases, latest

34 stable releases of shell-quote, oldest to newest.

## What happens

Impact

`quote()` 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 in that later string ends the comment, and the rest of the string is parsed as shell input:

```
quote(['echo', 'ok', { comment: 'x' }, 'a\nid;#']);
// echo ok #x 'a
// id;#'
```

Passed to `sh`, `bash`, `dash`, `ksh`, or `zsh`, this runs `id`.

`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.

Exploitation requires an attacker-controlled string containing a line terminator that follows a `{ comment }` token in the same `quote()` call.

Patches

Fixed in v1.11.0: `quote()` throws a `TypeError` when a string after a `{ comment }` token contains a line terminator (`\n`, `\r`, U+2028, or U+2029).

Workarounds

Drop every token after a `{ comment }` token before calling `quote()`, or reject line terminators in untrusted strings. Separately, do not append other shell text after `quote()` output that contains a comment, since the comment swallows it.

## How it is exploited

Exploitable over the network, with no account and no action from a user.

- **Confidentiality**: high
- **Integrity**: high
- **Availability**: high

CVSS:3.1/​AV:N/​AC:H/​PR:N/​UI:N/​S:U/​C:H/​I:H/​A:H

## References

- [Reference](https://github.com/ljharb/shell-quote/security/advisories/GHSA-pqg4-j6r4-53mv "https://github.com/ljharb/shell-quote/security/advisories/GHSA-pqg4-j6r4-53mv")  
github.com/ljharb/shell-quote/security/advisori…
- [NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-102422 "https://nvd.nist.gov/vuln/detail/CVE-2026-102422")  
nvd.nist.gov/vuln/detail/CVE-2026-102422
- [Fix commit](https://github.com/ljharb/shell-quote/commit/6002b2ed90c6b83095eb272b6b0adaf3a172b0bc "https://github.com/ljharb/shell-quote/commit/6002b2ed90c6b83095eb272b6b0adaf3a172b0bc")  
6002b2e
- [Package](https://github.com/ljharb/shell-quote "https://github.com/ljharb/shell-quote")  
github.com/ljharb/shell-quote