← Back
CVE-2026-73414
OS Command Injection in shescape (CVE-2026-73414)
Summary
OS command injection in shescape (CVE-2026-73414). Risk of unauthorized operations or information disclosure. Exploitable via ``shell``. Mitigation: upgrade to `3.0.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-73414** has been found in shescape.
Attackers can target a specific entry point like ``shell`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade shescape to **3.0.1** or later.
If unsure, ask your IT team or search "shescape CVE-2026-73414" on the vendor's site.
CVE-2026-73414 (shescape) — CWE-78 /
Attack surface: `shell` / `true` / `escape` / `escapeAll`
Patched: `3.0.1` — apply immediately
Workaround: Alternatively, users of Shescape can remove all instances of `(` and `)` from untrusted inputs.
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.
❓ What is the problem
**OS command injection** (CWE-78) exists in shescape. Attackers reach the vulnerable code path via ``shell`` without authentication.
📍 Affected scope
shescape — . Attack surface: `shell` / `true` / `escape` / `escapeAll`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **3.0.1**.
🛡️ Workaround
Workaround: Alternatively, users of Shescape can remove all instances of `(` and `)` from untrusted inputs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'shescape' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'shescape' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `shescape` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Alternatively, users of Shescape can remove all instances of `(` and `)` from untrusted inputs.パッチが適用されるまでの応急処置として、Alternatively, users of Shescape can remove all instances of `(` and `)` from untrusted inputs. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade shescape to 3.0.1ステージング環境で 3.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
npm
shescape
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.0.1"}]}]
References
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web [email protected]
- web https://github.com/ericcornelissen/shescape/blob/dea8893a5877893d8d4923dbf253080e08899e6d/docs/migration.md
- web [email protected]
- web [email protected]
- web https://github.com/advisories/GHSA-w4hw-qcx7-56pr