A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a GOAWAY frame. (CVE-2026-48937)
A vulnerability in the Node.js HTTP/2 server API allows servers to continue accepting data even after sending a GOAWAY frame. This issue affects Node.js versions prior to 22.23.0 and versions from 23.0.0 up to but not including 24.17.0. The flaw could lead to unexpected server behavior related to connection termination handling.
AI Analysis
Technical Summary
CVE-2026-48937 is a flaw in the Node.js HTTP/2 server API where the server improperly continues to accept data after issuing a GOAWAY frame, which is intended to signal the termination of a connection. This affects two supported release lines: Node.js 22 and Node.js 24, specifically versions <22.23.0 and >=23.0.0 <24.17.0. The vulnerability has been assigned a high severity rating. A patch is available to address this issue.
Potential Impact
The vulnerability may cause Node.js HTTP/2 servers to accept data beyond the intended connection termination point, potentially leading to resource exhaustion or unexpected server behavior. No known exploits are reported in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade affected Node.js versions to 22.23.0 or later, or 24.17.0 or later to remediate the issue.
A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a GOAWAY frame. (CVE-2026-48937)
Description
A vulnerability in the Node.js HTTP/2 server API allows servers to continue accepting data even after sending a GOAWAY frame. This issue affects Node.js versions prior to 22.23.0 and versions from 23.0.0 up to but not including 24.17.0. The flaw could lead to unexpected server behavior related to connection termination handling.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-48937 is a flaw in the Node.js HTTP/2 server API where the server improperly continues to accept data after issuing a GOAWAY frame, which is intended to signal the termination of a connection. This affects two supported release lines: Node.js 22 and Node.js 24, specifically versions <22.23.0 and >=23.0.0 <24.17.0. The vulnerability has been assigned a high severity rating. A patch is available to address this issue.
Potential Impact
The vulnerability may cause Node.js HTTP/2 servers to accept data beyond the intended connection termination point, potentially leading to resource exhaustion or unexpected server behavior. No known exploits are reported in the wild at this time.
Mitigation Recommendations
A patch is available for this vulnerability. Users should upgrade affected Node.js versions to 22.23.0 or later, or 24.17.0 or later to remediate the issue.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- BIT-node-2026-48937
- Osv Schema Version
- 1.6.2
- Aliases
- ["CVE-2026-48937"]
- Ecosystems
- ["Bitnami"]
- Database Specific Severity
- High
- Cvss Version
- null
Threat ID: 6a85b4a7acd9273b4925081c
Added to database: 08/19/2026, 13:50:31 UTC
Last enriched: 08/19/2026, 14:00:06 UTC
Last updated: 08/19/2026, 22:52:13 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.