critical CVSS 9

CVE-2026-48619·Node.js vulnerability

A flaw in Node.js HTTP/2 client allows a server to send an unlimited number of ORIGIN frames, which could lead to an Out of Memory error on the client. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

Severity
critical
Software
Node.js
Fixed in
20.19.2+dfsg-1+deb13u3
Published

Affected versions

Until: 20.19.2+dfsg-1+deb13u3

Fixed in: 20.19.2+dfsg-1+deb13u3

How to fix this CVE

Update Node.js to version 20.19.2+dfsg-1+deb13u3 or later to patch the HTTP/2 ORIGIN frame handling vulnerability. This vulnerability allows remote attackers to exhaust client memory by sending excessive ORIGIN frames, causing denial of service. Apply this update immediately to all systems running affected Node.js versions.

sudo dnf update nodejs

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

HTTP/2 ORIGIN frame flood pattern: repeated RST_STREAM or GOAWAY frames following multiple ORIGIN frame deliveries; process memory climbing linearly during HTTP/2 connection initialization; pattern: /ORIGIN.*ORIGIN.*ORIGIN/

How to check if you are affected

  1. Check installed Node.js version: node --version or nodejs --version
  2. Verify if HTTP/2 client functionality is enabled in your application: grep -r 'http2' your_app_directory or check package.json for http2 dependencies
  3. Search application logs for connection resets or memory errors: grep -E '(ORIGIN|OutOfMemory|ENOMEM|memory|exhausted)' /var/log/application.log
  4. After patching, confirm the update with: node --version and verify it shows version 20.19.2 or later

FAQ

What is CVE-2026-48619?

CVE-2026-48619 is a critical denial-of-service vulnerability in Node.js HTTP/2 client implementation where a malicious server can send unlimited ORIGIN frames to exhaust the client's memory and trigger a crash.

Is CVE-2026-48619 being actively exploited?

No, this vulnerability is not currently listed in the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available at this time.

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

Node.js versions prior to 20.19.2+dfsg-1+deb13u3 are affected, including Node.js 22, 24, and 26 according to the vendor advisory. Supported release lines across multiple major versions contain this flaw.

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

Run 'node --version' and compare against the fixed version 20.19.2+dfsg-1+deb13u3. If your version is older, your system is vulnerable. Additionally, check if HTTP/2 client features are in use with grep 'http2' in your application code.

Does Defensia detect CVE-2026-48619?

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-48619 will appear in your dashboard with remediation steps.

Related Node.js CVEs

CVE-2026-48930CVSS 10A 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-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-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-58042CVSS 9A flaw in Node.js can cause dns.resolveAny() Aborts the Node.js Process When a DNS Response Contains More Than 256 A Records. Repeated triggering of this condition can lead to denial of service. This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
CVE-2026-48933CVSS 9A flaw in Node.js WebCrypto implementation can crash the process if the input of `subtle.encrypt()` is a multiple of 2GiB. This vulnerability affects all supported release lines: **Node.js 22**, **Node.js 24**, and **Node.js 26**.

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-48619. Free for 1 server.

Get started free