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**.
Metrics
Affected Vendors & Products
References
History
Tue, 04 Aug 2026 19:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Node.js HTTP/2 Heap Use‑After‑Free via Re‑entrant Call |
Tue, 04 Aug 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 04 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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**. | |
| Weaknesses | CWE-416 | |
| References |
| |
| Metrics |
cvssV3_0
|
Status: PUBLISHED
Assigner: hackerone
Published:
Updated: 2026-08-04T17:36:14.044Z
Reserved: 2026-06-23T15:00:03.632Z
Link: CVE-2026-56848
Updated: 2026-08-04T17:36:05.963Z
No data.
No data.
OpenCVE Enrichment
Updated: 2026-08-04T19:30:05Z