Skip to content
Fencer Intel
high 8.1

CVE-2026-123872 json

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

published 16h ago modified 15h ago also EUVD-2026-123699

cvss
8.1
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
—
no EPSS score yet
public exploits
0
none known

Summary

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.

Patch / fix

  • nodejs node 22.23.5, 24.22.3, 26.13.1
  • nodejs Alpine 3.22, Alpine 3.21 22.23.5-r0
  • nodejs Alpine 3.24, Alpine 3.23 24.22.3-r0

alpine advisories ALPINE-CVE-2026-123872

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2026-123872 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-123872 updated cvss 8.1

nodejs: Node.js: Client certificate authentication bypass via TLS renegotiation

  • Red Hat Hardened Images nodejs25 25.9.0-1.7.hum1, nodejs20 20.20.2-1.3.hum1, nodejs24 24.22.2-0.2.hum1, nodejs26 26.13.0-0.1.1.hum1, nodejs22 22.23.4-2.3.2.3.1.hum1
    affected: workaround, no fix available, no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CVSS scores

assigned by version score vector
CNA 3.0 8.1 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Affected products

  • nodejs node

Classification

Weakness
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.