All CVEs

nginx2root (CVE-2026-123007, plus CVE-2026-123633): unauthenticated RCE (as the worker user, not root) in nginx 1.9.5–1.31.8 when HTTP/2 is enabled. Public exploit since 18 Nov, no attacks seen, not in KEV. Check: nginx -T | grep http2. Fix: 1.31.9 / 1.30.7 and restart, or set http2 off;. https://tldrcve.com/nginx2root/

nginx · CVE-2026-123007 · CVE-2026-123633

nginx2root

Patch now if…Only if HTTP/2 is on. Public exploit, no attacks yet.

A bug in nginx's HTTP/2 handling lets an attacker with no login crash nginx or run code as the nginx worker user. Despite the name, it doesn't give root by itself (Xint got root by chaining it with a separate Linux kernel bug, covered on our Linux SCTP root page), and code execution needs ASLR to be off or bypassed. A second HTTP/2 bug (CVE-2026-123633) is fixed by the same releases, and so are three other nginx bugs (HTTP/3, resolver, mail proxy) that Xint groups under the same name; turning off HTTP/2 doesn't cover those.

How scary is it?

updated 20 Nov
  • Yes: Works without logging in3,4
  • Yes: Public exploit code is out3,4
  • No: No attacks seen yet6
  • No: Not on CISA's exploited list7

Scare-o-meter

Check today

Find out if you're affected.
If you are, patch.

Are you affected? only if all are true

1nginx 1.9.5 – 1.31.8command

Stable 1.30.7 and later are fixed. Also NGINX Plus 37.0.0–37.0.7.1 and 37.1.0–37.2.0.1; older NGINX Plus R33–R36 get no fix (sources differ on R33), so move to 37.x. Distros backport fixes without changing nginx -v, so check the package against your distro's advisory. After upgrading, restart: a reload keeps the old binary.1,3,8,5,9

nginx -v
2HTTP/2 is on anywherecommand

Either http2 on; or listen ... http2, on any server block. Static-only sites count. Behind a proxy that terminates HTTP/2, the public exploit likely fails, but the bug is still there.1,3,4

sudo nginx -T 2>&1 | grep -nE 'listen[[:space:]].*http2|http2 on'

What to do

1Upgrade nginx

1.31.9 (mainline) or 1.30.7 (stable). NGINX Plus: 37.3.0.1 or 37.0.8.1. Debian (DSA-6642-1, DLA-4918-1) and Ubuntu (USN-9159-1) have fixed packages. Then restart.1,3,14,15,16,17

Latest safe versions checked 20 Nov

NGINX Plus → 37.x (CR)37.3.0.137.0 (LTS)37.0.8.1
nginx → 1.31 (mainline)1.31.91.30 (stable)1.30.7Older nginx lines get no fixes. NGINX Plus is listed separately, and products that bundle nginx have their own versions.
2Can't upgrade? Turn off HTTP/2command

Set http2 off; in each server block and remove http2 from every listen line (before 1.25.1, only the listen change). This breaks native gRPC, and doesn't cover the HTTP/3, resolver and mail-proxy bugs the same upgrade fixes.1,5

http2 off;
3Check bundled nginx

Kong, APISIX, NGINX Gateway Fabric and community ingress-nginx bundle nginx with HTTP/2 on by default. APISIX 3.21.0 and NGINX Gateway Fabric 2.9.0 are built on the fixed 1.31.9; F5's NGINX Ingress Controller 5.8.0 still ships 1.31.8. Community ingress-nginx gets no fixes after March 2026. Check with your vendor.6,10,11,12,13

This page shows you how to check. It can't tell you you're safe.

Sources (17) and changelog
  1. nginx.org: security advisories 18 Nov
  2. nginx.org: CHANGES
  3. Rapid7: NGINX Plus versions, exploit limits
  4. Rapid7: public exploit code 18 Nov
  5. Xint: original disclosure
  6. CSO Online: no attacks seen, forks
  7. CISA KEV catalog: not listed
  8. CVE record (F5): NGINX Plus R33+ affected, ASLR note
  9. Tenable FAQ: reload vs restart, NGINX Plus R33–R36
  10. Kubernetes: ingress-nginx retirement
  11. Apache APISIX 3.21.0: nginx 1.31.9 core, fixes it 19 Nov
  12. NGINX Gateway Fabric 2.9.0: built on nginx 1.31.9 18 Nov
  13. NGINX Ingress Controller 5.8.0: ships nginx 1.31.8
  14. Debian tracker: DSA-6642-1 fixed packages
  15. Ubuntu: USN-9159-1, all releases fixed
  16. CVE record (F5): CVE-2026-123633, HTTP/2 use-after-free when proxying 18 Nov
  17. Debian tracker: DLA-4918-1 and DSA-6642-1 fix both