CVE-2026-48619Network attack vector

Client crash via unbounded ORIGIN frame accumulation

Published Jun 26, 2026 · Updated Jun 26, 2026

Uncontrolled resource consumption in Node.js 22, 24, and 26 allows remote attackers to crash HTTP/2 clients via ORIGIN frames. The node:http2 client adds every origin advertised by server-sent ORIGIN frames to its session originSet without enforcing a size limit. Exploitation requires a Node.js client to connect to an attacker-controlled HTTP/2 server, which can exhaust process memory and terminate that client.

CVSS severity5.3
Medium
EPSS probability0.64%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Uncontrolled resource consumption in Node.js 22, 24, and 26 allows remote attackers to crash HTTP/2 clients via ORIGIN frames. The node:http2 client adds every origin advertised by server-sent ORIGIN frames to its session originSet without enforcing a size limit. Exploitation requires a Node.js client to connect to an attacker-controlled HTTP/2 server, which can exhaust process memory and terminate that client.

The record

CVE
CVE-2026-48619
Published
Jun 26, 2026
Updated
Jun 26, 2026
Vendor
Node.js
Product
Node.js
Classifications
CWE-400, T1499.004
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jun 26, 2026CVE publishedPublication date reported by the CVE source.
  2. Jun 26, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=22.22.3 <=22.22.3
  2. Affected versionversion=24.16.0 <=24.16.0
  3. Affected versionversion=26.3.0 <=26.3.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

Node.js · Node.jsversion=22.22.3 <=22.22.3; version=24.16.0 <=24.16.0; version=26.3.0 <=26.3.0

Published CVSS scores

7.5NVDCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
5.3HackerOneCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-400Uncontrolled Resource Consumption
T1499.004Application or System Exploitation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo