{"id":"CVE-2026-102422","url":"https://www.cyber-defence.io/tools/cve/CVE-2026-102422","generatedAt":"2026-10-27T22:46:44.562Z","title":"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.","description":"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.","published":"2026-09-29T04:17:56.000Z","lastModified":"2026-09-30T17:32:07.000Z","status":"Deferred","sourceIdentifier":"7ffcee3d-2c14-4c3e-b844-86c6a321a158","cvss":{"version":"4.0","score":9.2,"severity":"CRITICAL","vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/M"},"cwe":["CWE-78"],"affected":[],"epss":{"score":0.00378,"percentile":0.31501,"date":"2026-10-26","history":[{"date":"2026-09-29","score":0.00383,"percentile":0.29703}]},"kev":{"listed":false},"exploits":{"count":0,"verified":false,"firstPublished":null,"source":"Exploit-DB (https://gitlab.com/exploit-database/exploitdb)","entries":[]},"verdict":{"level":"high","text":"High impact if exploited, but EPSS currently rates exploitation as unlikely (0.38%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit."},"changes":[{"kind":"new","label":"New CVE","at":"2026-09-29T04:17:56.000Z","detail":{"score":"9.2","severity":"CRITICAL","publishedAt":"2026-09-29T04:17:55.707Z"},"summary":"New CVE, critical severity (CVSS 9.2)."}],"references":[{"url":"https://github.com/ljharb/shell-quote","source":"7ffcee3d-2c14-4c3e-b844-86c6a321a158"},{"url":"https://github.com/ljharb/shell-quote/commit/6002b2ed90c6b83095eb272b6b0adaf3a172b0bc","source":"7ffcee3d-2c14-4c3e-b844-86c6a321a158"},{"url":"https://github.com/ljharb/shell-quote/security/advisories/GHSA-pqg4-j6r4-53mv","source":"7ffcee3d-2c14-4c3e-b844-86c6a321a158"},{"url":"https://www.npmjs.com/package/shell-quote","source":"7ffcee3d-2c14-4c3e-b844-86c6a321a158"}],"sources":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-102422","epss":"https://www.first.org/epss/","kev":"https://www.cisa.gov/known-exploited-vulnerabilities-catalog","exploitdb":"https://www.exploit-db.com/"},"licence":"CC BY 4.0 — link back to the CVE Explorer if you publish the results; upstream data remains subject to its own terms."}