CVE-2026-48937

CVE Enrichment

CVSS: 7.5 HIGH
EPSS: 0.57%
EPSS Percentile: 46.67%
CISA KEV: Not listed

Description

A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` frame. This vulnerability affects two supported release lines: **Node.js 22** and **Node.js 24**.

Technical Details

CVSS Version: 3.1
CNA / NVD Source: [email protected]
Published: 19-Jun-2026 02:16
Last Modified: 19-Aug-2026 00:54
EPSS Date: 2026-10-24
CWE: CWE-400

CVSS Vector


            CVSS:3.1                            AV:N /
                            AC:L /
                            PR:N /
                            UI:N /
                            S:U /
                            C:N /
                            I:N /
                            A:H

Affected Products / Versions

nodejs / node.js
Version / affected range: * · from (inclusive) 22.0 · before (exclusive) 22.23.0
cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*
nodejs / node.js
Version / affected range: * · from (inclusive) 24.0.0 · before (exclusive) 24.17.0
cpe:2.3:a:nodejs:node.js:*:*:*:*:-:*:*:*

References

Last enrichment sync: 25-Oct-2026 01:01
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE-2026-48937 in Node.js shows how this plays out. The fix shipped alongside a semver-major update to nghttp2 that removed HTTP/2 priority signaling entirely, because the vulnerable behavior and the removed feature Practical Guidance for Prioritizing and Remediating Vulnerabilities

CVE (1)

MITRE ATT&CK (1)

Vendors (2)

Products (8)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.