Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-48937: CWE-400 Uncontrolled Resource Consumption in nodejs node

0
Medium
VulnerabilityCVE-2026-48937cvecve-2026-48937cwe-400
Published: Thu Jun 18 2026 (06/18/2026, 18:01:39 UTC)
Source: CVE Database V5
Vendor/Project: nodejs
Product: node

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**.

CVSS v3.0

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Affected software

GitHub Actionsmore threats →ai
nodejs/node
pkg:github/nodejs/node
Affected versions
=22.22.3=24.16.0

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

AILast updated: 06/18/2026, 19:05:48 UTC

Technical Analysis

This vulnerability in Node.js HTTP/2 server API causes the server to keep accepting data after sending a GOAWAY frame, which should normally signal the termination of the connection. This behavior can lead to uncontrolled resource consumption (CWE-400), potentially causing denial of service conditions. The issue affects specific versions 22.22.3 and 24.16.0 of Node.js. The CVSS 3.0 base score is 5.3, reflecting a medium impact primarily on availability. No known exploits are reported in the wild, and no official fix or patch has been documented at this time.

Potential Impact

The vulnerability can cause denial of service by exhausting server resources due to continued data acceptance after a GOAWAY frame. There is no impact on confidentiality or integrity. The affected versions are limited to Node.js 22.22.3 and 24.16.0. No known active exploitation has been reported.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is released, monitor for updates from the Node.js project. No temporary or official fixes have been documented in the provided data.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
hackerone
Date Reserved
2026-05-26T15:00:06.427Z
Cvss Version
3.0
State
PUBLISHED
Remediation Level
null

Threat ID: 6a343e63f198dc38c151df59

Added to database: 6/18/2026, 6:52:19 PM

Last enriched: 6/18/2026, 7:05:48 PM

Last updated: 6/18/2026, 10:41:22 PM

Views: 23

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses