Vulnerability in node-shell-quote (UBUNTU-CVE-2026-9277)
Summary
Vulnerability in node-shell-quote (UBUNTU-CVE-2026-9277). Successful exploitation can lead to full system takeover. Exploitable via envFn. Mitigation: upgrade to 1.7.4+~1.7.1-1ubuntu0.24.04.1 or later.
Original description
The description as published by the source.
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.
Source: OSV.dev (Open Source Vulnerabilities) OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as UBUNTU-CVE-2026-9277 has been found in node-shell-quote.
Attackers can target a specific entry point like envFn over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade node-shell-quote to 1.7.4+~1.7.1-1ubuntu0.24.04.1 or later.
If unsure, ask your IT team or search "node-shell-quote UBUNTU-CVE-2026-9277" on the vendor's site.
UBUNTU-CVE-2026-9277 (node-shell-quote)
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: envFn / pattern / comment / TypeError
Patched: 1.7.4+~1.7.1-1ubuntu0.24.04.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (unclassified) exists in node-shell-quote. Attackers reach the vulnerable code path via envFn without authentication.
Check the vendor advisory for the affected versions of node-shell-quote. Attack surface: envFn / pattern / comment / TypeError.
Severity: ?. Successful exploitation can lead to full system takeover.
Update to 1.7.4+~1.7.1-1ubuntu0.24.04.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'node-shell-quote' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'node-shell-quote' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
node-shell-quoteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade node-shell-quote to 1.7.4+~1.7.1-1ubuntu0.24.04.1ステージング環境で 1.7.4+~1.7.1-1ubuntu0.24.04.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory ubuntu.com
- report ubuntu.com
- report cve.org
- report github.com
- report github.com
- report github.com
- report npmjs.com
- report openwall.com
- report github.com