Skip to content
VulniPulse
High8.1Red Hat Linux

CVE-2026-123872: Red Hat Client certificate authentication bypass via TLS renegotiation

This Red Hat advisory covers CVE-2026-123872. Related products: Red Hat Hardened Images.

Open the Red Hat advisory

Key facts

Vendor rating
High, CVSS 8.1
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, .
CISA KEV
Not listed (catalogue checked )
Fixed in
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 and 4 more below
Source published
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Related products & platforms

Red Hat LinuxUnclassified

Description

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.

Text from the source record.

How to fix CVE-2026-123872

Upgrade to a fixed release named by 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
  • RHSA-2026:99433

Vendor 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.

CVE-2026-123872 in other vendors' advisories

Compare every advisory for CVE-2026-123872

All Red Hat Linux advisories

Get an email when Red Hat publishes the next one.

See Red Hat'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 Red Hat