← Back
CVE-2026-49860
medium
CVSS 5.2
SSRF (Server-Side Request Forgery) in deno (CVE-2026-49860)
Summary
SSRF in deno (CVE-2026-49860). Risk of unauthorized operations or information disclosure. Exploitable via ``localhost``. Mitigation: upgrade to `2.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-49860** has been found in deno.
Attackers can target a specific entry point like ``localhost`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.2/10.
What to do: upgrade deno to **2.8.1** or later.
If unsure, ask your IT team or search "deno CVE-2026-49860" on the vendor's site.
CVE-2026-49860 (deno) — CWE-918 / CVSS v3 5.2
Attack vector: local / no user interaction
Attack surface: `localhost` / `Deno.connect`
Patched: `2.8.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.
❓ What is the problem
**SSRF** (CWE-918) exists in deno. Attackers reach the vulnerable code path via ``localhost`` without authentication.
📍 Affected scope
deno — . Attack surface: `localhost` / `Deno.connect`.
🔥 Severity
Severity: Medium (CVSS 5.2/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **2.8.1**.
🛡️ 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.8.1ステージング環境で 2.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.8.1"}]}]