Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-48937: A flaw in Node.js HTTP/2 server API can cause servers to keep accepting data even after sending a `GOAWAY` fra

43
This month
HIGH 7.5REMOTEUPGRADE

CVE-2026-48937 is a high-severity flaw (CVSS 7.5) affecting node.js. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.6% (top 53%)
CISA exploited listNo
WeaknessCWE-400
Published2026-06-18
Last modified2026-10-25
Publisher (CNA): HackerOne · Vendor: nodejs

Share: LinkedIn · X · Reddit

Last updated 2026-10-25 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

nodejs node.js UPGRADE
Affected: >= 22.0 and < 22.23.0 · >= 24.0.0 and < 24.17.0
Fixed in: 22.23.0, 24.17.0
Safe to downgrade to: a release before 22.0
1. Check installed version
apt-cache policy node.js || rpm -q node.js || node.js --version
2. UPGRADE to 22.23.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade node.js
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade node.js
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 22.0 (Debian / Ubuntu)
apt-cache madison node.js sudo apt install node.js=<VERSION_BEFORE_22.0> sudo apt-mark hold node.js
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list node.js sudo dnf downgrade node.js-<VERSION_BEFORE_22.0> sudo dnf versionlock add node.js
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-48937?

node.js: upgrade to 22.23.0, 24.17.0. Exact commands for each OS are on this page.

Is CVE-2026-48937 being exploited?

CVE-2026-48937 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-48937 affect?

CVE-2026-48937 affects node.js. Severity is high (CVSS 7.5). 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**.

How urgent is CVE-2026-48937?

Priority 43/100. High severity; Remotely exploitable, no login, no user action

Software pages

Node.js vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.