Two different failures sit behind one update

The Node.js project released fixes for supported 22.x, 24.x and 26.x lines on 11 November. CVE-2026-123863 can let an unauthenticated client abort an affected HTTP/2 server on 24.x or 26.x. CVE-2026-123866 concerns HTTP/2 stream teardown and can send freed response memory to a peer, potentially including data from other connections. The conditions for the latter differ by release line and how a stream is closed.

The release also includes other security fixes beyond HTTP/2. It is worth applying as a supported runtime update, but an article about these two flaws should not imply every Node.js application presents the same attack path.

Scope matters

A service that terminates HTTP/2 before requests reach Node may have a different exposure from one using Node's built-in HTTP/2 server. Check the architecture before assigning urgency.

Use the runtime and traffic path as your checklist

  1. 1

    Find running versions. Inventory deployed Node.js processes and container images, then separate supported 22.x, 24.x and 26.x services from end-of-life releases.

  2. 2

    Identify exposed features. Check whether each service uses Node's built-in HTTP/2 or affected TLS behavior. Do not infer that from a front-end proxy alone.

  3. 3

    Update and recycle. Move to 22.23.5, 24.22.3 or 26.13.1 as appropriate, rebuild images and restart processes. Verify the version running after rollout.

A library update cannot replace a runtime rollout

Teams often update a lockfile and assume the application is covered. These are Node.js runtime fixes. Trace the deployed image or host package, then check the process that serves traffic. For a memory-disclosure issue, keep investigation claims modest unless there is independent evidence of misuse.