CVE-2026-120993
Description
A flaw was found in NGINX. When configured to process stream traffic using dynamic certificate loading and the PROXY protocol, an abbreviated SSL (Secure Sockets Layer) handshake can cause a worker process to terminate unexpectedly. A remote attacker can exploit this flaw to cause a Denial of Service (DoS) on the server.
Statement
This vulnerability is rated as Moderate impact because an abnormal handshake only causes worker process termination rather than remote code execution or unauthorized data disclosure. In standard Red Hat deployments, NGINX is not susceptible by default, as exploitation requires an uncommon stream configuration that concurrently enables dynamic certificate resolution and PROXY protocol version 2. Furthermore, the master process automatically restarts terminated workers, preventing persistent denial of service unless a malicious client generates sustained traffic.
Mitigation
To mitigate this vulnerability, apply one of the following configuration changes to affected stream configurations:
1. Replace dynamic certificate loading:
Avoid using variables in the `ssl_certificate` and `ssl_certificate_key` directives within the stream context. Define explicit static file paths for certificates and private keys within individual `server` blocks.
2. Remove PROXY protocol version 2:
If backend metadata forwarding is not strictly necessary, remove or disable the `proxy_protocol` directive within the affected stream `proxy_pass` blocks.
After editing `/etc/nginx/nginx.conf` or the relevant configuration file in `/etc/nginx/conf.d/`, validate the configuration and reload the service:
nginx -t
systemctl reload nginx
3. Restrict network access:
Limit incoming traffic to the stream proxy port to trusted client IP addresses using firewalld:
firewall-cmd --permanent --zone=trusted --add-source=<trusted_ip_or_range>
firewall-cmd --reload
Warning:
Reloading the NGINX service or firewalld applies configuration changes immediately. Always run `nginx -t` to verify syntax before reloading to prevent configuration errors from interrupting service availability.
Caveats:
Using static certificate directives requires separate server blocks for each domain, which increases administrative overhead. Disabling PROXY protocol disables client IP and port propagation to backend stream targets. Restricting network access blocks untrusted or public clients from reaching the stream service.
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 | 5.3 | N/A | 5.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | None | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | None |
| Integrity Impact | None | N/A | None |
| Availability Impact | Low | N/A | Low |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Understanding the Weakness (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart
NULL pointer dereferences usually result in the failure of the process unless exception handling (on some platforms) is available and implemented. Even when exception handling is being used, it can still be very difficult to return the software to a safe state of operation.
Integrity,Confidentiality
Technical Impact: Execute Unauthorized Code or Commands; Read Memory; Modify Memory
In rare circumstances, when NULL is equivalent to the 0x0 memory address and privileged code can access it, then writing or reading memory is possible, which may lead to code execution.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.