Skip to main content
VulnerabilityPublished

CVE-2026-48937: nodejs node · Uncontrolled Resource Consumption

Affects nodejs nodeSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium.

Data as of 1 Nov 2026, 08:20 UTC

CVSS 3.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
nodejsnodeAffected
  • >=22.22.3 <=22.22.3
  • >=24.16.0 <=24.16.0
Fixed in–

AI-suggested

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.

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

References

Community reviews

Loading reviews…