shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token
### 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: ```js 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.
- Products
- shell-quote
- Affected versions
- Not specified
- Fixed versions
- 1.11.0
- CVEs
- CVE-2026-102422
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 27 Oct 2026, 11:19 UTC · Revision 1
Source evidence
shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token
core-osv · Original sourcePublished 6 Oct 2026, 13:40 UTC
### 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: ```js 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.
osv:GHSA-pqg4-j6r4-53mv
shell-quote
Fixed versions: 1.11.0
Complete source record
{
"id": "ea306187436dbfebaafd9893b202b8326e7bae94ba7e7c23c605b121d37551f6",
"url": "https://osv.dev/vulnerability/GHSA-pqg4-j6r4-53mv",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "shell-quote: `quote()` command injection via a line terminator in a token after a `{ comment }` token",
"summary": "### 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: ```js 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.",
"evidence": "osv:GHSA-pqg4-j6r4-53mv",
"products": [
{
"name": {
"value": "shell-quote",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.11.0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "critical",
"structured": {
"id": "GHSA-pqg4-j6r4-53mv",
"aliases": [
"CVE-2026-102422",
"GHSA-pqg4-j6r4-53mv"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H"
},
{
"type": "CVSS_V4",
"score": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "1.8.4"
},
{
"fixed": "1.11.0"
}
]
}
],
"package": {
"name": "shell-quote",
"purl": "pkg:npm/shell-quote",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-pqg4-j6r4-53mv/GHSA-pqg4-j6r4-53mv.json"
}
}
],
"modified": "2026-10-06T13:45:06.393196831Z",
"provider": "osv",
"references": [
"https://github.com/ljharb/shell-quote/security/advisories/GHSA-pqg4-j6r4-53mv",
"https://nvd.nist.gov/vuln/detail/CVE-2026-102422",
"https://github.com/ljharb/shell-quote/commit/6002b2ed90c6b83095eb272b6b0adaf3a172b0bc",
"https://github.com/ljharb/shell-quote"
],
"provider_metadata": {
"cwe_ids": [
"CWE-78"
],
"severity": "CRITICAL",
"github_reviewed": true,
"nvd_published_at": "2026-09-29T04:17:55Z",
"github_reviewed_at": "2026-10-06T13:40:36Z"
}
},
"related_cves": [
{
"value": "CVE-2026-102422",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 89087,
"published_at": "2026-10-06T13:40:36+00:00"
}