A flaw in Node.js HTTP/2 handling allows nghttp2_session_mem_send() to be called re-entrantly while nghttp2_session_mem_recv() is executing, resulting in a heap-use-after-free.
This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Weakness
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory “belongs” to the code that operates on the new pointer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | RedHat | nodejs22-1:22.23.2-1.el10_2 | * |
| Red Hat Enterprise Linux 10 | RedHat | nodejs24-1:24.19.0-1.el10_2 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | nodejs22-1:22.23.2-1.el10_0 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:22-8100020260819113925.6d880403 | * |
| Red Hat Enterprise Linux 8 | RedHat | nodejs:24-8100020260819113942.6d880403 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:22-9080020260819113937.rhel9 | * |
| Red Hat Enterprise Linux 9 | RedHat | nodejs:24-9080020260819113946.rhel9 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | nodejs:22-9060020260901085634.rhel9 | * |