CVE-2026-120967
Description
A flaw was found in NGINX. A remote attacker can bypass client certificate verification when the service is configured to require client certificates in a non-default stream virtual server. This vulnerability allows unauthorized clients to establish connections and access restricted stream services without presenting a valid certificate.
Statement
Red Hat Product Security rates this vulnerability as Moderate because exploitation requires a specialized, non-standard configuration and impact is strictly restricted to data-plane access control bypass. Standard Red Hat deployments of NGINX typically serve HTTP workloads or operate stream proxying without granular per-virtual-server mutual TLS (mTLS) enforcement. Environments are only susceptible when secondary stream server blocks enforce mandatory client certificate validation, leaving the control plane and underlying host system unaffected.
Mitigation
Restrict network access to the port hosting the affected stream service using firewalld so that only trusted client IP addresses or subnets can establish connections.
1. Add the authorized client IP address or network range to the trusted firewall zone:
# firewall-cmd --permanent --zone=trusted --add-source=192.0.2.0/24
2. Remove public exposure of the stream service port:
# firewall-cmd --permanent --zone=public --remove-port=8443/tcp
3. Apply the firewall configuration:
# firewall-cmd --reload
Caveats: Restricting network access by source IP address requires maintaining an accurate allowlist of authorized client networks and is unsuitable for public-facing deployments with dynamic client IP addresses.
Warning: Reloading the firewall configuration can temporarily disrupt active network connections.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.8 | N/A | 4.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | Low | N/A | Low |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
Understanding the Weakness (CWE)
Integrity,Authentication
Technical Impact: Bypass Protection Mechanism; Gain Privileges or Assume Identity
When a certificate is invalid or malicious, it might allow an attacker to spoof a trusted entity by interfering in the communication path between the host and client. The product might connect to a malicious host while believing it is a trusted host, or the product might be deceived into accepting spoofed data that appears to originate from a trusted host.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.