NODE.JS · CVE-2026-123828 · Runtime
NO FIX YET
Node.js writes one byte past a heap buffer in HTTP/2 Alt-Svc handling when an app passes an attacker-controlled value such as the :authority header to Http2Session.altsvc(). A single long but valid request can abort the process and corrupt heap memory.
first public Nov 11, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Exposure requires an HTTP/2 server built on Node.js 24.x or 26.x that passes attacker-controlled input, such as the :authority header, into Http2Session.altsvc(). Applications that do not call altsvc() with request-derived values are not described as affected. The sources do not state a fixed version.
Not affected if no-altsvc-with-request-input
Who cares http2, nodejs, servers
node --version and check whether it reports 24.x or 26.x.Http2Session.altsvc( and check whether the origin comes from request headers such as :authority.No fix yet, per the sources.
A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in src/node_http2.cc allocates a buffer sized to the origin length and then writes it with a null terminator, placing one byte past the end of the allocation. A single request carrying a long but syntactically valid :authority triggers the out-of-bounds write, which aborts the process and serves as a remote heap-corruption primitive. This vulnerability affects Node.js 26.x and 24.x.
This page as .md · .json · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.