Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to vulnerabilities
Unrated

Node.js HTTP/2 server sessions fail to clean up after GOAWAY

IdentifiersCVE-2026-48937CWE-404

CVE-2026-48937 is a medium-severity flaw in the Node.js HTTP/2 server API affecting the supported 22.x and 24.x release lines. According to the provided content, when an invalid protocol error occurs and the server sends an HTTP/2 GOAWAY frame, the affected implementation can fail to properly clean up the session and may continue accepting data after shutdown has been initiated. In other words, the HTTP/2 session lifecycle is not correctly terminated after GOAWAY under these error conditions, resulting in improper connection cleanup and continued processing on a session that should be closing.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial
ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

An attacker interacting with an affected Node.js HTTP/2 server can cause the server to continue accepting or processing data after the server has initiated connection shutdown with GOAWAY. This can lead to improper connection handling and may contribute to denial-of-service conditions or other security issues arising from stale or incompletely terminated HTTP/2 sessions.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure of Node.js HTTP/2 server endpoints to untrusted clients, disable or avoid use of the HTTP/2 server functionality where operationally feasible, and place affected services behind controls that limit abusive or malformed protocol interactions. These are temporary risk-reduction measures only; the primary mitigation is upgrading to a fixed version.

Remediation

Patch, then assume compromise.

Upgrade Node.js to a fixed release. The provided content states that the June 18, 2026 security updates fixed this issue in Node.js v22.23.0 and v24.17.0. End-of-life versions should not be relied upon, as they may remain vulnerable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
NodejsNodejsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

5 SOURCESView more in app
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Start free trial
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity3

Community discussion across Reddit, Mastodon, and other social sources.

EXTERNAL REFERENCES
MITRE CVE
cve.org · CVE-2026-48937
NVD
nvd.nist.gov/vuln/detail/CVE-2026-48937
MITRE CWE · CWE-404
cwe.mitre.org