GHSA-m526-rv55-w6mr
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessConnect to TLS/HTTP server
-
DeliverySend crafted writes including empty writes
-
ExploitTrigger nested parser execution
-
ExecutionCause use-after-free in parser
-
ImpactCrash service or corrupt memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires network reachability to a Node.js process using the affected TLS/HTTP server/parser path, against versions prior to the fixed releases (before 22.23.5 on the 22.x line, before 24.22.3 on the 23/24.x line, and before 26.13.1 on the 25/26.x line). The specific trigger involves a write pattern containing empty writes that causes nested parser execution leading to the use-after-free; the exact sequence is not described in the available sources. Limiting factors: the vendor-assigned AC:H indicates the condition is hard to reach reliably, no authentication is modeled (PR:N) so no credentials are needed, and no user interaction is required (UI:N). The only complete remediation stated by the vendor is upgrading to the fixed versions. |
| Impact | This is a genuinely high-severity issue that warrants prompt but not emergency attention. The vendor-supplied CVSS 3.0 vector (CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H, 8.1) indicates a network-reachable flaw requiring no privileges or user interaction, with a changed scope and primary impact on availability (A:H) plus limited confidentiality and integrity (C:L/I:L) - a profile consistent with the CWE-416 use-after-free in the TLS/HTTP parser. The high attack complexity (AC:H) signals that triggering the nested-parser-execution-from-empty-writes condition is not trivially reliable, which tempers real-world weaponization. No EPSS score, CISA KEV listing, or SSVC decision array was supplied, and there is no public exploit identified at time of analysis; the only prioritization signal is the aggregator Decision label 'this_week'. There is no conflict between signals here, but key exploitation-probability data (EPSS) and active-exploitation data (KEV) are simply ABSENT rather than low - treat the absence as unknown, not as evidence of safety. Given Node.js's ubiquity, the net assessment is a real priority to patch on a near-term (this-week) cadence, with the AC:H constraint and lack of observed exploitation arguing against emergency out-of-band action. |
| Exploit ScenarioDerived | A remote attacker who can establish TLS/HTTP connections to a Node.js server crafts a sequence of writes - including empty writes - that induces nested execution of the parser, triggering a use-after-free. Because the CVSS marks AC:H, reliably reaching the freed-memory condition is difficult and likely requires precise timing or crafted framing. No public exploit is identified at time of analysis, and the exact trigger is not described in the available sources beyond the commit title 'prevent nested parser execution from empty writes'. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 11, 2026
Use-after-free in Node.js TLS and HTTP handling allows remote, unauthenticated attackers to trigger nested parser execution through write patterns containing empty writes, corrupting freed parser state and risking process crash, memory corruption and limited information exposure on exposed servers. Affected lines are 22.x before 22.23.5, the 23/24.x line before 24.22.3 and the 25/26.x line before 26.13.1, tracked under CVSS 8.1 where the vendor-assigned AC:H reflects that the condition is hard to reach reliably (PR:N, UI:N, scope changed). No public exploit code and no confirmed active exploitation were identified at time of analysis, but the vendor states that upgrading to a fixed release is the only complete remediation.
RemediationAI
Vendor-released patch: upgrade to Node.js 22.23.5 on the 22.x line, 24.22.3 on the 23/24.x line, or 26.13.1 on the 25/26.x line - these are the fixed versions stated in the vendor advisory (https://nodejs.org/en/blog/vulnerability/november-2026-security-releases), with release details at https://github.com/nodejs/node/releases/tag/v26.13.1. The vendor states that updating is the only complete fix for this issue, so rebuild container images and managed runtime baselines from the patched releases rather than pinning older tags, and confirm the effective runtime version inside each deployed artifact since the flaw spans multiple branches with different fix versions. Prioritization should follow the vuln.today 'this_week' decision label - prompt remediation is warranted, but the hard-to-reach trigger keeps it below emergency handling; the exposed surface is limited to processes that accept network connections through the Node.js TLS/HTTP server paths, so internet-facing services should be patched ahead of internal-only ones.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a use-after-free (CWE-416) in the interaction between Node.js' TLS and HTTP layers. Empty writes fed into these paths cause the parser to be re-entered while it is still executing, so state that is being released can be reached again and used after free - the classic memory-safety pattern that can turn into a crash or memory corruption rather than clean connection teardown. The exact call sequence and the precise conditions that make the re-entrancy reachable are not described in the available sources; the vendor's AC:H metric only indicates the triggering condition is hard to achieve reliably, and the scope-changed rating (S:C) reflects impact escaping the vulnerable component to the hosting process. The fix appears in the 2026-11-11 security release alongside a cluster of related HTTP/2 and TLS memory-safety fixes (header release on stream removal, streams abandoned by nghttp2, buffer retention during pending socket writes, ALTSVC buffer overflow, TLS SNI/resumption handling), which points to the parser and stream lifetime bookkeeping in Node.js' HTTP stack as the underlying technical area. Affected deployments are any Node.js server that terminates TLS or serves HTTP through these built-in modules.
Know when the next one hits your stack
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
Network-reachable parser flaw needing no auth or interaction (AV:N/PR:N/UI:N); hard-to-trigger nested-write condition (AC:H); UAF in a scope-crossing parser yields availability-dominant impact with limited C/I.
Primary rating from Vendor (CNA).
CVSS VectorVendor
Lifecycle Timeline
2Description PRE-NVD
Executive ViewAI
CVE-2026-123864 is a high-severity use-after-free vulnerability in Node.js TLS and HTTP handling that can be triggered by remote, unauthenticated attackers, potentially causing server crashes, memory corruption, and limited information exposure. This affects any internet-facing Node.js services using the vulnerable versions, and while exploitation is difficult due to the high attack complexity, a successful attack could disrupt critical business services and put sensitive data at risk. Leadership should prioritize patching to maintain service availability and protect organizational assets.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-123683
NVD
CVE.org
EPSS
Exploit-DB