← Back
CVE-2026-49402
high
CVSS 8.1
OS Command Injection in deno (CVE-2026-49402)
Summary
OS command injection in deno (CVE-2026-49402). Successful exploitation can lead to full system takeover. Exploitable via ``spawn``. Mitigation: upgrade to `2.7.10` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49402** has been found in deno.
Attackers can target a specific entry point like ``spawn`` over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.1/10.
What to do: upgrade deno to **2.7.10** or later.
If unsure, ask your IT team or search "deno CVE-2026-49402" on the vendor's site.
CVE-2026-49402 (deno) — CWE-78 / CVSS v3 8.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `spawn` / `spawnSync` / `exec` / `cmd.exe`
Patched: `2.7.10` — 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.
❓ What is the problem
**OS command injection** (CWE-78) exists in deno. Attackers reach the vulnerable code path via ``spawn`` without authentication.
📍 Affected scope
deno — . Attack surface: `spawn` / `spawnSync` / `exec` / `cmd.exe`.
🔥 Severity
Severity: High (CVSS 8.1/10). Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.7.10**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'deno' .` 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 'deno' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `deno` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade deno to 2.7.10ステージング環境で 2.7.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
rust
deno
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.7.10"}]}]