Vulnerability in Node.js HTTP/2 server API (CVE-2026-48937)
Summary
Vulnerability in Node.js HTTP/2 server API (CVE-2026-48937). Risk of unauthorized operations or information disclosure. Exploitable via GOAWAY.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48937 has been found in Node.js HTTP/2 server API.
Attackers can target a specific entry point like GOAWAY over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Node.js HTTP/2 server API CVE-2026-48937" on the vendor's site.
CVE-2026-48937 (Node.js HTTP/2 server API) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: GOAWAY
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-400) exists in Node.js HTTP/2 server API. Attackers reach the vulnerable code path via GOAWAY without authentication.
Check the vendor advisory for the affected versions of Node.js HTTP/2 server API. Attack surface: GOAWAY.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Node.js HTTP/2 server API を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-48937 nodejs Fixed in: 22.23.0-r0
- Debian DEBIAN-CVE-2026-48937 nodejs
- Ubuntu UBUNTU-CVE-2026-48937 nodejs
References
- advisory hackerone.com
- advisory nodejs.org
- web nvd.nist.gov
- web github.com