Security alert · High
nginx HTTP/2 flaw (CVE-2026-123007) can crash workers or allow code execution
· 4 minutes read · Centoculus Security Team
Known since
Affected: NGINX Open Source and NGINX Plus with HTTP/2 enabled. See the vendor advisory for affected and fixed versions.
What happened
On 18 November 2026, a vulnerability in NGINX Open Source and NGINX Plus became public. It is tracked as CVE-2026-123007 and has a CVSS base score of 8.1 (high).
The problem is in HTTP/2 handling. When nginx processes certain traffic, which has not been disclosed, the HTTP/2 flow control window can go over its allowed limit. This can cause a heap buffer overflow, which usually crashes the nginx worker process with a segmentation fault. The attacker may also be able to run code on the server. This works if Address Space Layout Randomization (ASLR) is turned off, or if the attacker can get around ASLR.
According to the vendor, this affects the data plane only, not the control plane. An attacker could use it to crash worker processes, corrupt their memory or possibly run code remotely.
The vulnerability is not listed as actively exploited. Our source data has no confirmed attacks.
Who is affected
- Servers running NGINX Open Source or NGINX Plus with HTTP/2 enabled, for example through
http2 on;orlisten ... http2. - Servers where nginx does not use HTTP/2 are not affected by this issue.
- Software built on nginx may also be affected, for example OpenResty or ingress-nginx. The reference links include issues and fixes for these projects, so check with the vendor of your product.
- The vendor did not evaluate versions that have reached End of Technical Support (EoTS). If you run one of these, plan an upgrade to a supported version.
Our source data does not list the affected and fixed versions. Check the F5 advisory (K000163926), the nginx changelog and your distribution's security advisory, all linked below.
What to do now
- Find out whether HTTP/2 is active. Run
nginx -T 2>/dev/null | grep -n http2. If you get no output, this issue does not affect that server. - Install the fixed nginx version. If you use distribution packages, run
apt update && apt install --only-upgrade nginxordnf update nginx, as soon as your distribution offers the update. If you use the nginx.org repositories or NGINX Plus, upgrade to the fixed version named in the F5 advisory. - Back up your configuration (
/etc/nginx), then check it withnginx -t. - Restart nginx so that no old worker processes keep running:
systemctl restart nginx. Then check that the service is running withsystemctl status nginxand that your sites respond. - If you cannot update yet, you can turn off HTTP/2 for the time being. Remove
http2from thelistendirectives or sethttp2 off;, then reload nginx. Clients will fall back to HTTP/1.1. - Make sure ASLR is enabled.
cat /proc/sys/kernel/randomize_va_spaceshould return2. This does not fix the flaw, but it makes code execution harder. - Update other products that are based on nginx, such as OpenResty, ingress-nginx and container images, as soon as their maintainers release fixes.
How to check whether you are affected
nginx -vshows the installed version. Compare it with the versions in the F5 advisory or your distribution's advisory.nginx -T 2>/dev/null | grep http2shows whether HTTP/2 is configured.- Check the nginx error log, usually
/var/log/nginx/error.log, for lines such asworker process ... exited on signal 11. Check the system journal (journalctl -u nginx) for crashes too. Worker crashes that keep happening without explanation can be a sign that someone is trying to exploit this flaw. They are not proof of an attack.
Update November 20, 2026
Update, 20 November 2026: News reports published on 19 November describe two critical NGINX flaws, dubbed "nginx2root", that let unauthenticated attackers run code on web servers. According to the reports, researchers showed how to chain them with a Linux kernel bug to gain root on the server. The report does not name CVE IDs or affected versions, so we cannot yet confirm whether CVE-2026-123007 is one of the two flaws or whether the fixed version in the steps above covers both. Follow the steps above. Also install your distribution's kernel updates and restart into the new kernel, and watch the F5 advisory and your distribution's advisories for any further nginx fixes.
Sources
More sources (7)
- https://access.redhat.com/security/cve/cve-2026-123007
- https://cyberscoop.com/nginx-critical-vulnerabilities-exploits/
- https://github.com/advisories/GHSA-m4q8-cf44-f42r
- https://github.com/chainguard-forks/ingress-nginx/pull/69
- https://github.com/nginx/nginx/commit/b89c4100bf6762a45e4a6463eaf4b70368277c94
- https://github.com/nginx/nginx/issues/2002
- https://github.com/openresty/openresty/issues/1165
If you run web servers, also check
Related posts
Alerts ·
WordPress plugin vulnerabilities: 8 plugins, including WPvivid Backup
Vulnerabilities in eight WordPress plugins were disclosed on 20 November 2026, among them WPvivid Backup, NextGEN Gallery and Optimole. The most serious, in Mang Board, lets unauthenticated visitors delete board posts.
Alerts ·
Drupal core: critical installer flaw can allow site takeover without login
Drupal fixed a critical flaw in the built-in installer (install.php). Under specific conditions it lets attackers without a login reinstall a site and take it over. Update to 10.6.22, 11.3.22 or 11.4.13, and block the installer.
Alerts ·
VMware vCenter Server: critical authentication bypass fixed after zero-day attacks
Broadcom has fixed a critical authentication bypass in VMware vCenter Server (VMSA-2026-0009). Mandiant says it was used in zero-day attacks from early September 2026. vCenter 8.0, 9.0 and 9.1 are affected. ESX hosts are not.