Skip to main content

Node.js CVE-2026-123864

| EUVDEUVD-2026-123683 HIGH
Use After Free (CWE-416)
8.1
CVSS 3.0 · Vendor
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Connect to TLS/HTTP server
  2. Delivery
    Send crafted writes including empty writes
  3. Exploit
    Trigger nested parser execution
  4. Execution
    Cause use-after-free in parser
  5. Impact
    Crash 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'.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Node 0.0.0 <22.23.5
Node 25.0.0 <26.13.1
Node 23.0.0 <24.22.3

Affected Packages

euvd node fix: 22.23.5, 24.22.3, 26.13.1

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

Vendor (CNA) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
vuln.today AI 8.1 HIGH

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.

3.1 AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N
Red Hat 7.4 HIGH

Primary rating from Vendor (CNA).

CVSS VectorVendor

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
High

Lifecycle Timeline

2
CVE Published
Nov 11, 2026 - 16:44 github-releases
HIGH 8.1
CVE Published
Nov 11, 2026 - 16:44 github-releases
UNKNOWN (no severity yet)

Description PRE-NVD

Disclosed via GitHub release of nodejs/node. NVD scoring and full description are pending.

Executive ViewAI

Why It Matters

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.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 73% exploitable
Prevalence
Ubiquitous
Node.js is a core runtime deployed across a huge fraction of server environments
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
High

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

Vendor StatusVendor

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy