VulnerabilityPublished 11 Nov 2026

CVE-2026-123872: nodejs node · Improper Authentication – Generic

Affects nodejs nodeSource CVE Database V5

Compare

Not known to be exploited · CVSS 8.1 High · fixed in 26.13.1 : patch nodejs node soon.

Data as of 11 Nov 2026, 18:49 UTC

CVSS 3.0 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (openjs)	CVSS 3.0	8.1

Patch: Available – fixed in 26.13.1, 24.22.3, 22.23.5

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade nodejs node to 26.13.1, 24.22.3 or 22.23.5.

Affected software

Product	Affected	Fixed in
nodejsnode	Affected >=25.0.0 <26.13.1	Fixed in 26.13.1
nodejsnode	Affected >=23.0.0 <24.22.3	Fixed in 24.22.3
nodejsnode	Affected <22.23.5	Fixed in 22.23.5

AI-suggested

Upgrade Node.js to versions 22.23.5, 24.22.3, or 26.13.1 or later where this vulnerability is fixed. No other mitigation is indicated or required as the fix addresses the authentication bypass.

Description

CVE-2026-123872 is a high-severity vulnerability in Node.js affecting versions 22.x, 24.x, and 26.x. It allows a client to bypass client certificate authentication by changing the servername during TLS 1.2 renegotiation. This enables the client to access endpoints with stricter client-certificate policies by carrying over authentication from a less restricted host. The issue is fixed in Node.js versions 22.23.5, 24.22.3, and 26.13.1.

Impact

An attacker with client certificate authentication on a less restricted hostname can bypass stricter client certificate policies on other hostnames by renegotiating the TLS 1.2 connection with a different servername. This leads to unauthorized access to protected endpoints, compromising confidentiality and integrity of the affected services. The vulnerability has a CVSS 3.0 score of 8.1 (high severity), indicating a network attack vector with low complexity and no user interaction required, but requiring some privileges.

Summary

This vulnerability in Node.js TLS implementation permits a client to alter the servername during TLS 1.2 renegotiation, bypassing client certificate authentication policies that vary by hostname. Specifically, a client authenticated on a host with a less strict policy can renegotiate the connection to a host with stricter client-cert requirements and reuse the existing authentication, effectively bypassing the stricter controls. The flaw affects Node.js versions 22.x, 24.x, and 26.x prior to the fixed releases 22.23.5, 24.22.3, and 26.13.1.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Nov 2026, 18:49 UTC

Technical details

References

Community reviews

Related threats