概要
認証なしで、サーバのメモリや接続を解放されないまま溜めさせられるおそれ。
元の説明(英語)を読む
An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
影響を受ける人
HTTP/2 を使う Node.js 22・24・26 の管理者
対策
- Node.js を 22.23.5・24.22.3・26.13.1 のいずれか以降に更新する
国内の動き
本文に同じ CVE 番号のある国内の注意喚起・報道は、まだ無い。
海外の動き
- The Hacker News(報道)↗11/12
PoC
公開されている PoC は、まだ見つかっていない。