← Back
CVE-2026-48615
high
CVSS 7.5
Vulnerability in node (CVE-2026-48615)
Summary
vulnerability in node (CVE-2026-48615). Confidential information can be exposed externally. Exploitable via ``ERR_PROXY_TUNNEL``. Mitigation: upgrade to `22.23.0, 24.17.0, 26.3.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48615** has been found in node.
Attackers can target a specific entry point like ``ERR_PROXY_TUNNEL`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.5/10.
What to do: upgrade node to **22.23.0, 24.17.0, 26.3.1** or later.
If unsure, ask your IT team or search "node CVE-2026-48615" on the vendor's site.
CVE-2026-48615 (node) — CWE-359 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: `ERR_PROXY_TUNNEL`
Patched: `22.23.0, 24.17.0, 26.3.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
**A vulnerability** (CWE-359) exists in node. Attackers reach the vulnerable code path via ``ERR_PROXY_TUNNEL`` without authentication.
📍 Affected scope
node — . Attack surface: `ERR_PROXY_TUNNEL`.
🔥 Severity
Severity: High (CVSS 7.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **22.23.0, 24.17.0, 26.3.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 'node' .` 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 'node' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `node` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade node to 22.23.0, 24.17.0, 26.3.1ステージング環境で 22.23.0, 24.17.0, 26.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Bitnami
node
[{"type":"SEMVER","events":[{"introduced":"22.22.3"},{"fixed":"22.23.0"},{"introduced":"24.16.0"},{"fixed":"24.17.0"},{"introduced":"26.3.0"},{"fixed":"26.3.1"}]}]
Bitnami
node-min
[{"type":"SEMVER","events":[{"introduced":"22.22.3"},{"fixed":"22.23.0"},{"introduced":"24.16.0"},{"fixed":"24.17.0"},{"introduced":"26.3.0"},{"fixed":"26.3.1"}]}]