Skip to content
VulniPulse
High 2 vendors · 2 advisories

CVE-2026-123872: Node.js is vulnerable to a client certificate authentication bypass via TLS 1.2 renegotiation servername change

CVE-2026-123872 key facts

CISA KEV
Not listed (catalogue checked )
Highest advisory rating
High
CVSS base score
8.1 (NetApp), 8.1 (Red Hat)
CVSS vector
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N · base score 8.1, scored by openjsAttack vector: network. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: none.
Weakness
  • CWE-287 Improper Authentication - Generic
EPSS
0.41% chance of exploitation in the next 30 days (35th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
Fixed releases
  • Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1 and 1 more in the advisory
Vendor advisories
2 from NetApp, Red Hat
Assigned by
openjs (CNA)
CVE record published
Listed by VulniPulse
Record changed

Ratings, versions and fixes are quoted from the vendor advisories that cover only CVE-2026-123872; each belongs to its advisory, not to every product listed. How records are collected and checked.

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.

Text from the CVE.org record (openjs).

How do I fix CVE-2026-123872?

Upgrade to a fixed release named by the vendor:

  • Red Hat: nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1, nodejs24-main-11.19.1-1.24.22.3.0.1.hum1, nodejs26-main-26.13.1-0.1.hum1
  • Enforce TLS 1.3 to eliminate TLS renegotiation, or isolate virtual host policies using an upstream reverse proxy. To enforce TLS 1.3 across Node.js services without application code modifications, configure the minimum TLS version using the NODE_OPTIONS environment variable: ``` export NODE_OPTIONS="--tls-min-v1.3" ``` For systemd-managed Node.js applications, configure the environment variable within the unit configuration: ``` [Service] Environment="NODE_OPTIONS=--tls-min-v1.3" ``` Apply the configuration by reloading systemd and restarting the target service: ``` systemctl daemon-reload systemctl restart ``` Caveats: Enforcing TLS 1.3 prevents clients that support only TLS 1.2 or earlier from establishing connections. Applying systemd configuration changes and restarting the service will cause a momentary service interruption. Alternatively, if TLS 1.2 support must be retained, terminate TLS connections at a reverse proxy configured to bind differing mutual TLS authentication domains to separate listening addresses or ports. (Red Hat)

Vendor advisories for CVE-2026-123872

NetApp

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-123872] Node.js Vulnerability in NetApp Products

    NTAP-20261120-0008Source published Source updated

    Node.js versions 22.x prior to 22.23.5, 24.x prior to 24.22.3 and 26.x prior to 26.13.1 are susceptible to a vulnerability which when successfully exploited could allow a remote authenticated attacker to bypass client certificate authentication controls during TLS 1.2 renegotiation and gain unauthorized access to otherwise protected resources. Successful exploitation of this vulnerability could lead to disclosure of sensitive information or addition or modification of data. NetApp reports that one or more additional products remain under investigation; review the canonical advisory for current status. NetApp states there is no workaround available at this time.

    Affected products in this advisory
    No product details extracted. Check the source bulletin.
    Source-reported affected versions
    • 22.23.5
    • 24.22.3
    • 26.13.1
    Source-reported fixed versions
    No fixed-version detail extracted. This does not mean no fix exists.
    Mitigation guidance
    No mitigation guidance extracted; consult the source.

Red Hat

1 advisory
  • Advisory severityHigh8.1

    High [CVE-2026-123872] Client certificate authentication bypass via TLS renegotiation

    CVE-2026-123872Source published Source updated

    Client certificate authentication bypass via TLS renegotiation. Red Hat rates this important (CVSS 8.1). Weakness: CWE-287. Red Hat lists fixing advisory RHSA-2026:99433 with package nodejs24-main-24.22.3-0.1.hum1, nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1, nodejs22-main-22.23.5-2.3.2.3.1.hum1, nodejs26-main-11.20.0-1.26.13.1.0.1.hum1. Affected product named by the advisory: Red Hat Hardened Images.

    Related products — impact not confirmed
    • Red Hat Hardened Images
    Source-reported affected versions
    Affected-version details not available in this record.
    Source-reported fixed versions
    • nodejs24-main-24.22.3-0.1.hum1
    • nodejs22-main-10.9.9-1.22.23.5.2.3.2.3.1.hum1
    • nodejs22-main-22.23.5-2.3.2.3.1.hum1
    • nodejs26-main-11.20.0-1.26.13.1.0.1.hum1

    3 more entries in the full advisory.

    Mitigation guidance
    • Enforce TLS 1.3 to eliminate TLS renegotiation, or isolate virtual host policies using an upstream reverse proxy. To enforce TLS 1.3 across Node.js services without application code modifications, configure the minimum TLS version using the NODE_OPTIONS environment variable: ``` export NODE_OPTIONS="--tls-min-v1.3" ``` For systemd-managed Node.js applications, configure the environment variable within the unit configuration: ``` [Service] Environment="NODE_OPTIONS=--tls-min-v1.3" ``` Apply the configuration by reloading systemd and restarting the target service: ``` systemctl daemon-reload systemctl restart <service_name> ``` Caveats: Enforcing TLS 1.3 prevents clients that support only TLS 1.2 or earlier from establishing connections. Applying systemd configuration changes and restarting the service will cause a momentary service interruption. Alternatively, if TLS 1.2 support must be retained, terminate TLS connections at a reverse proxy configured to bind differing mutual TLS authentication domains to separate listening addresses or ports.

References

Timeline

  1. CVE record published
  2. First vendor advisory listed by VulniPulse
  3. CVE record last updated

All NetApp advisories

Get an email when NetApp publishes the next one.

See NetApp's last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about NetApp