Sign in Sign up
JA · EN · FR
SecPulse
← Back
CVE-2026-21710 high CVSS 7.5

Vulnerability in node (CVE-2026-21710)

Summary

vulnerability in node (CVE-2026-21710). Risk of unauthorized operations or information disclosure. Exploitable via ``TypeError``. Mitigation: upgrade to `20.20.2, 22.22.2, 24.14.1, 25.8.2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2026-21710** has been found in node. Attackers can target a specific entry point like ``TypeError`` over the network to misuse the product. Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10. What to do: upgrade node to **20.20.2, 22.22.2, 24.14.1, 25.8.2** or later. If unsure, ask your IT team or search "node CVE-2026-21710" on the vendor's site.
CVE-2026-21710 (node) — CWE-770 / CVSS v3 7.5 Attack vector: remote (network-reachable) / unauthenticated / no user interaction Attack surface: `TypeError` / `__proto__` / `req.headersDistinct` / `Object.prototype` Patched: `20.20.2, 22.22.2, 24.14.1, 25.8.2` — 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-770) exists in node. Attackers reach the vulnerable code path via ``TypeError`` without authentication.
📍 Affected scope
node — . Attack surface: `TypeError` / `__proto__` / `req.headersDistinct` / `Object.prototype`.
🔥 Severity
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **20.20.2, 22.22.2, 24.14.1, 25.8.2**.
🛡️ 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

  1. 1
    Identify exposure identify 
    grep -r 'node' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `node` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch 
    Upgrade node to 20.20.2, 22.22.2, 24.14.1, 25.8.2

    ステージング環境で 20.20.2, 22.22.2, 24.14.1, 25.8.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

Bitnami node
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"20.20.2"},{"introduced":"21.0.0"},{"fixed":"22.22.2"},{"introduced":"23.0.0"},{"fixed":"24.14.1"},{"introduced":"25.0.0"},{"fixed":"25.8.2"}]}]
Bitnami node-min
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"20.20.2"},{"introduced":"21.0.0"},{"fixed":"22.22.2"},{"introduced":"23.0.0"},{"fixed":"24.14.1"},{"introduced":"25.0.0"},{"fixed":"25.8.2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →