Skip to main content
No exploitation reportedAwaiting NVD analysis

CVE-2026-123872

Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change

No exploitation reported by the sources we read.

  • Published2026-11-11
  • WeaknessCWE-287

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Timeline

dates in UTC
  1. 2026-11-1118:30CVE publishedCNA

Versions per branch

Products declared by the CNA

As openjs, the CNA that assigned this CVE, declared them in the CVE record; versions as written. NVD lists no product for this CVE yet: this is the only product data so far.

  • nodejs nodeother versions: not affected
    Affected
    • ≥ 0.0.0, < 22.23.5fixed in 22.23.5semver
    • ≥ 23.0.0, < 24.22.3fixed in 24.22.3semver
    • ≥ 25.0.0, < 26.13.1fixed in 26.13.1semver

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2026-11-11

Neither OSV.dev nor the vendor advisories we read list affected versions for CVE-2026-123872 yet.

Full record on NVD

Fix

No fix published by the sources we read yet. NVD record

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

  • NVDCVE recordread 2026-11-11
  • CNACVSS 3.08.12026-11-11
  • CNAweakness (CWE)CWE-2872026-11-11

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Published
2026-11-11
Last Modified
2026-11-11
NVD status
Received

Frequently asked questions

What is CVE-2026-123872?

A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x.

Is CVE-2026-123872 actively exploited?

Active exploitation of CVE-2026-123872 has not been confirmed.

What is the CVSS score for CVE-2026-123872?

CVE-2026-123872 has a CVSS v3 base score of 8.1 (HIGH severity), with vector string CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record