high CVSS 8.1

CVE-2026-123007·Nginx vulnerability

This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Severity
high
Software
Nginx
Fixed in
1.30.7
Published

Affected versions

From: 1.9.5

Until: 1.30.6

Fixed in: 1.30.7

How to fix this CVE

Upgrade Nginx to version 1.30.7 or later to patch the HTTP/2 flow control vulnerability that can cause worker process crashes or memory corruption. Organizations running Nginx Plus or Open Source with HTTP/2 enabled should prioritize this update, as the vulnerability allows remote attackers to trigger heap buffer overflows without authentication. Verify the upgrade was successful and restart the Nginx service to apply the fix. Hosted Power publishes patched nginx packages that carry the complete nginx2root fixes for Debian 8 Jessie through 13 Trixie, CentOS 7 (archived EPEL) and CentOS 8 AppStream (streams 1.14, 1.16, 1.18 and 1.20), under the MIT licence: https://github.com/HOSTED-POWER/nginx2root-patches. These are not a mitigation and need no follow-up: each package is that release's own nginx source with every nginx2root patch that applies to it, so nothing further is required. For Debian 8 to 11 and CentOS 7 and 8 no official update is coming at all, which makes them the fix rather than a stand-in. On Debian 12 and 13, where an official update may still ship, the package version deliberately sorts below Debian's expected one (for example 1.22.1-9+deb12u10.1~hp1 on Bookworm) so apt takes over cleanly when it arrives, with no pinning. Patches, checksums, tests and reproducible build instructions are public; we checked the repository on 19 November 2026 (v1.3.2). Note that disabling HTTP/2 does not address the resolver and mail proxy issues in this set. Enterprise Linux is covered too, as of 19 November 2026: RHEL 8 and Rocky Linux 8 (the nginx:1.24 module stream); RHEL 9, Rocky Linux 9 and Oracle Linux 9 across the base 1.20 stream and AppStream 1.22, 1.24 and 1.26; AlmaLinux 9's retired 1.22 stream; and RHEL, Rocky Linux and Oracle Linux 10. On the 10 releases the situation differs by vendor and it matters: AlmaLinux 10 has shipped an official fix, while RHEL 10 and Rocky Linux 10 have not — both still ship nginx 1.26.3-16.el10_3.1, which predates the disclosure. Do not assume a current EL 10 system is patched because a sibling distribution is.

sudo dnf update nginx

Defensia detects this vulnerability

How to check if you are affected

  1. Step 1: Check the installed Nginx version with `nginx -v` or `nginx -V` to display full configuration including HTTP/2 support.
  2. Step 2: Verify HTTP/2 is enabled by checking the Nginx configuration files (typically `/etc/nginx/nginx.conf` or `/etc/nginx/sites-enabled/*`) for `http2` directives in listen statements.
  3. Step 3: Search Nginx error logs for segmentation faults or worker process crashes using `grep -i 'segmentation\|worker.*exited' /var/log/nginx/error.log | tail -50`.
  4. Step 4: After patching, confirm the version with `nginx -v` returns 1.30.7 or higher, then validate configuration with `sudo nginx -t` and restart with `sudo systemctl restart nginx`.
  5. Step 5: If your distribution backported the fix, the version number will not show it. Debian, Ubuntu and the RHEL family ship security fixes inside the existing upstream release — Ubuntu's nginx 1.24.0-2ubuntu7.20 carries this fix and still answers "nginx/1.24.0" — so every version check above, and every external scanner, will keep calling a patched host vulnerable. Read the changelog of the package that is actually installed, which names the CVE: `zgrep -i CVE-2026-123007 /usr/share/doc/nginx*/changelog.Debian.gz` on Debian and Ubuntu, or `rpm -q --changelog nginx | grep -i CVE-2026-123007` on RHEL, Rocky, AlmaLinux and Oracle Linux. Use the file on disk rather than `apt changelog`: that command reads repository metadata, so it describes what the repository holds rather than what you are running, and it does not reliably show third-party packages — including backported ones. A match means this build carries the fix. The reverse does not hold: a CVE absent from the changelog may simply never have applied to that build, so absence is not confirmation that you are exposed.

FAQ

What is CVE-2026-123007?

This vulnerability affects Nginx when processing HTTP/2 traffic, allowing the flow control window to exceed safety limits and trigger a heap buffer overflow in the worker process. Attackers can crash the worker, corrupt memory, or potentially execute arbitrary code on systems with ASLR disabled.

Is CVE-2026-123007 being actively exploited?

No, this vulnerability is not currently listed on CISA's Known Exploited Vulnerabilities (KEV) catalog, and no public exploits are available. However, the high CVSS score of 8.1 and remote exploitability make prompt patching essential.

What versions of Nginx are affected by CVE-2026-123007?

All Nginx Plus and Open Source versions prior to 1.30.7 are vulnerable when HTTP/2 is enabled. Organizations must upgrade to 1.30.7 or later to remediate the issue.

How do I check if my server is vulnerable to CVE-2026-123007?

Run `nginx -v` to check your version, then verify HTTP/2 is active by inspecting configuration files for `http2` directives. If the version is below 1.30.7 and HTTP/2 is enabled, your server is vulnerable.

Does Defensia detect CVE-2026-123007?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Nginx is installed on a monitored server, CVE-2026-123007 will appear in your dashboard with remediation steps.

Related Nginx CVEs

CVE-2009-3555CVSS 10The TLS protocol, and the SSL protocol 3.0 and possibly earlier, as used in Microsoft Internet Information Services (IIS) 7.0, mod_ssl in the Apache HTTP Server 2.2.14 and earlier, OpenSSL before 0.9.8l, GnuTLS 2.8.5 and earlier, Mozilla Network Security Services (NSS) 3.12.4 and earlier, multiple Cisco products, and other products, does not properly associate renegotiation handshakes with an existing connection, which allows man-in-the-middle attackers to insert data into HTTPS sessions, and possibly other types of sessions protected by TLS or SSL, by sending an unauthenticated request that is processed retroactively by a server in a post-renegotiation context, related to a "plaintext injection" attack, aka the "Project Mogul" issue.
CVE-2026-60005CVSS 9NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module. When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart. Impact: This vulnerability may allow remote, unauthenticated attackers to have limited control to disclose memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only. Note: The ngx_http_slice_module module is not enabled by default; it's enabled with the --with-http_slice_module configuration parameter. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2026-49975CVSS 9Memory Allocation with Excessive Size Value vulnerability in Apache HTTP Server's mod_http leads to denial of service via malicious HTTP requests. This issue affects Apache HTTP Server: from 2.4.17 through 2.4.67.
CVE-2026-42946CVSS 9A vulnerability exists in the ngx_http_scgi_module and ngx_http_uwsgi_module modules that may result in excessive memory allocation or an over-read of data. When scgi_pass or uwsgi_pass is configured, an unauthenticated attacker with man-in-the-middle (MITM) ability to control responses from an upstream server may be able to read the memory of the NGINX worker process or restart it.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
CVE-2021-23017CVSS 9A security issue in nginx resolver was identified, which might allow an attacker who is able to forge UDP packets from the DNS server to cause 1-byte memory overwrite, resulting in worker process crash or potential other impact.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-123007. Free for 1 server.

Get started free