critical CVSS 9 EPSS 25%

CVE-2026-21710·Node.js vulnerability

A flaw in Node.js HTTP request handling causes an uncaught `TypeError` when a request is received with a header named `__proto__` and the application accesses `req.headersDistinct`. When this occurs, `dest["__proto__"]` resolves to `Object.prototype` rather than `undefined`, causing `.push()` to be called on a non-array. This exception is thrown synchronously inside a property getter and cannot be intercepted by `error` event listeners, meaning it cannot be handled without wrapping every `req.headersDistinct` access in a `try/catch`. * This vulnerability affects all Node.js HTTP servers on **20.x, 22.x, 24.x, and v25.x**

Severity
critical
Software
Node.js
Fixed in
18.20.4+dfsg-1~deb12u2
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 25% — in the top 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Affected versions

Until: 18.20.4+dfsg-1~deb12u2

Fixed in: 18.20.4+dfsg-1~deb12u2

How to fix this CVE

Update Node.js to version 18.20.4 or later to fix a critical HTTP header parsing flaw that can cause unhandled TypeErrors. This vulnerability allows specially crafted HTTP requests with a `__proto__` header to crash Node.js HTTP servers when accessing `req.headersDistinct`. Immediate patching is essential for all production HTTP servers running affected versions.

sudo dnf update -y nodejs

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

HTTP request containing header name `__proto__` (case-sensitive or case-insensitive variants) followed by application access to `req.headersDistinct` property, resulting in process exit with TypeError in HTTP server logs

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch.

WAF rule: Block HTTP requests containing the literal header name `__proto__` before they reach the Node.js application. Example rule: Deny if any request header name matches regex `^__proto__$` (case-insensitive).

How to check if you are affected

  1. Check the installed Node.js version: `node --version` and compare against 18.20.4 (or verify the package version via `apt show nodejs` or `dnf info nodejs`)
  2. Identify Node.js HTTP servers: grep for `http.createServer()`, `express()`, or `app.listen()` in your application code and configuration files
  3. Review HTTP server access logs for requests containing `__proto__` in header names: `grep -i '__proto__' /var/log/nodejs/*.log /var/log/http/*.log 2>/dev/null`
  4. Verify the patch by running `node --version` after update and confirming it shows 18.20.4+dfsg-1~deb12u2 or higher

FAQ

What is CVE-2026-21710?

CVE-2026-21710 is a critical vulnerability in Node.js HTTP request handling where HTTP headers named `__proto__` are misinterpreted as prototype pollution, triggering an uncaught TypeError when applications access the `req.headersDistinct` property. This causes the HTTP server to crash immediately without allowing standard error handlers to catch the exception.

Is CVE-2026-21710 being actively exploited?

No, CVE-2026-21710 is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available. However, the vulnerability is trivial to exploit and organizations should not rely on this for delay.

What versions of Node.js are affected by CVE-2026-21710?

Node.js versions 20.x, 22.x, 24.x, 25.x, and earlier versions up to 18.20.3 are affected. The vulnerability is fixed in Node.js 18.20.4 and corresponding patch releases for other LTS branches.

How do I check if my server is vulnerable to CVE-2026-21710?

Run `node --version` and compare against 18.20.4. If your version is older than 18.20.4, your server is vulnerable. Additionally, check if your Node.js application uses `req.headersDistinct` anywhere in the codebase.

Does Defensia detect CVE-2026-21710?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Node.js is installed on a monitored server, CVE-2026-21710 will appear in your dashboard with remediation steps.

Related Node.js CVEs

CVE-2026-21636CVSS 10A flaw in Node.js's permission model allows Unix Domain Socket (UDS) connections to bypass network restrictions when `--permission` is enabled. Even without `--allow-net`, attacker-controlled inputs (such as URLs or socketPath options) can connect to arbitrary local sockets via net, tls, or undici/fetch. This breaks the intended security boundary of the permission model and enables access to privileged local services, potentially leading to privilege escalation, data exposure, or local code execution. * The issue affects users of the Node.js permission model on version v25. In the moment of this vulnerability, network permissions (`--allow-net`) are still in the experimental phase.
CVE-2026-111497CVSS 9.8A buffer overflow vulnerability in the Brotli decoder (c/dec/decode.c) in Google Brotli versions 1.0.3 through 1.2.0 on all platforms allows a remote unauthenticated attacker to corrupt adjacent decoder state memory, disclose sensitive memory contents, cause a denial of service, or potentially execute arbitrary code using a crafted Brotli-compressed stream. Users need to update any Brotli libraries or binaries between 1.0.3 through 1.2.0 to the latest available version: 1.0.10 or 1.1.1 or 1.2.1.
CVE-2026-48930CVSS 9.8A flaw in Node.js TLS hostname handling can cause Embedded-nul hostnames can lead to silent authority rebinding due to c-string truncation in resolver bindings. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.
CVE-2025-55130CVSS 9.1A flaw in Node.js’s Permissions model allows attackers to bypass `--allow-fs-read` and `--allow-fs-write` restrictions using crafted relative symlink paths. By chaining directories and symlinks, a script granted access only to the current directory can escape the allowed path and read sensitive files. This breaks the expected isolation guarantees and enables arbitrary file read/write, leading to potential system compromise. This vulnerability affects users of the permission model on Node.js v20, v22, v24, and v25.
CVE-2026-56846CVSS 9A flaw in Node.js HTTP/2 handling can cause HTTP/2 retained header blocks evade maxSessionMemory and enable remote memory exhaustion. This vulnerability affects Node.js **24.x** and **22.x**.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-21710. Free for 1 server.

Get started free