Skip to content
VulniPulse
Medium5.3Red Hat Linux Updated

CVE-2026-120993: Red Hat CVE-2026-120993

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

Open the Red Hat advisory

Key facts

Vendor rating
Medium, CVSS 5.3
CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N · base score 6.9, scored by f5Attack vector: network. Attack complexity: low. Attack requirements: none. Privileges required: none. User interaction: none. Confidentiality impact on the vulnerable system: none. Integrity impact on the vulnerable system: none. Availability impact on the vulnerable system: low. Confidentiality impact on subsequent systems: none. Integrity impact on subsequent systems: none. Availability impact on subsequent systems: none.
Weakness
  • CWE-476 NULL Pointer Dereference
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Fixed in
nginx-main-1.30.6-1.hum1, RHSA-2026:83427
Source published
Listed by VulniPulse

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

Related products & platforms

Red Hat LinuxUnclassified

Description

CVE-2026-120993. Red Hat rates this moderate (CVSS 5.3).

Weakness: CWE-476. Red Hat lists fixing advisory RHSA-2026:83427 with package nginx-main-1.30.6-1.hum1.

Affected product named by the advisory: Red Hat Hardened Images.

Text from the source record.

How to fix CVE-2026-120993

Upgrade to a fixed release named by Red Hat:

  • nginx-main-1.30.6-1.hum1
  • RHSA-2026:83427

Vendor guidance

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

CVE-2026-120993 in other vendors' advisories

Compare every advisory for CVE-2026-120993

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