Tuskira AdvisoryNot observedLast updatedNovember 18, 2026

CVE-2026-123007

How to tell if CVE-2026-123007 and CVE-2026-123633 (NGINX HTTP/2) are reachable in your environment

Latest change
November 18: nginx.org released 1.30.7 and 1.31.9. Rapid7 published proof-of-concept code for CVE-2026-123007.

Reachable if an NGINX server with HTTP/2 on a client-facing listener runs a build without the November 18 fix and untrusted clients can reach it. No login is needed. CVE-2026-123633 also needs NGINX proxying to a backend

Affected
NGINX Open Source before 1.30.7 and 1.31.9, and NGINX Plus before the fixed 37.x builds, with HTTP/2 on. BIG-IP and F5OS are not affected, per F5
Exploitation
No exploitation reported. Not on CISA KEV. Rapid7, which disclosed CVE-2026-123007 with F5, has published proof-of-concept code on GitHub. Wiz and Xint have not released their exploits.
Fix
NGINX Open Source 1.30.7 or 1.31.9; NGINX Plus 37.0.8.1 or 37.3.0.1. Restart after upgrading.
Can't patch today
Turn off HTTP/2 on affected listeners, per Wiz and Xint. F5 lists no workaround

If you run an affected NGINX Open Source or NGINX Plus build with HTTP/2 enabled on a reachable listener, assume it is exposed until you install the fixed build. F5 disclosed two HTTP/2 flaws on November 18, 2026, and nginx.org released the fixes, NGINX Open Source 1.30.7 and 1.31.9, the same day. Ubuntu and Debian have not shipped fixed packages yet. Until you can upgrade, Wiz and Xint both say to turn HTTP/2 off.

F5 rates both flaws 8.1 High on CVSS 3.1 and calls the attack hard to pull off. It also gives both 9.2 Critical on CVSS 4.0. F5 says code execution needs ASLR disabled or bypassed. Wiz says it got remote code execution with ASLR bypassed on official NGINX 1.31.7 and 1.31.8 builds serving ordinary static files over HTTP/2, with no login and no backend application. Xint, Theori's research arm, reports the same for CVE-2026-123007. CVE-2026-123633 also needs NGINX to be proxying to a backend while the worker is running low on connections.

No exploitation has been reported, and neither CVE is on CISA's Known Exploited Vulnerabilities catalog. Rapid7, which disclosed CVE-2026-123007 with F5, published proof-of-concept code on GitHub on November 18. Rapid7 says it built the code for a freshly started test server and expects it to fail against busy or proxied ones. Wiz and Xint have not released their exploits.

Is it reachable for you?

What it is. Both flaws are in NGINX's HTTP/2 handling. CVE-2026-123007 lets a client push a counter past its limit, which corrupts memory and usually crashes the worker, per F5. CVE-2026-123633 frees memory that is still in use when a busy reverse proxy runs short of connections, per F5. F5 says either can lead to code execution when ASLR is disabled or bypassed. Wiz says the memory access these bugs give is enough to get past ASLR. Rapid7 says its own exploit needs about 128 GB of HTTP/2 traffic over a fast connection and may not work through a proxy.

Who is most exposed. Any internet-facing NGINX server or load balancer with HTTP/2 on. Wiz showed it against a server doing nothing more than serving static files. Reverse proxies are also exposed to CVE-2026-123633. Products that ship NGINX inside them, such as appliances and container images, are in scope too.

Checks, in three tiers. The first two decide exposure. The third decides priority. Run these only on systems your organization owns.

  1. Is HTTP/2 on? Run nginx -T and look for http2 on a listen directive or an http2 on line. If neither appears on any listener that clients reach, these two flaws are out of scope.
  2. Is the build unfixed? nginx -v below 1.30.7 on the stable line, or below 1.31.9 on mainline, is affected. Distribution packages backport fixes without changing that number, so compare the package version against your distribution's advisory, per Xint. Check container images and products that bundle NGINX.
  3. Can untrusted clients reach it? No login is needed. Internet-facing servers go first, then reverse proxies, since they are also exposed to CVE-2026-123633.
What Tuskira checks for this flaw in your environment
Internet-facing NGINX servers with HTTP/2 on and a build without the November 18 fix
What those NGINX servers and reverse proxies can reach
Across every system you run.
See how Tuskira finds exposed systems

Compensating controls (test them, don't assume them)

F5 lists no workaround. Wiz and Xint both give the same stopgap.

  • Turn off HTTP/2. Set http2 off in affected server blocks on NGINX 1.25.1 or later, and remove http2 from listen directives, per Wiz. Reload, then confirm the old worker processes have exited, per Wiz. Turn HTTP/2 back on after upgrading. Xint notes this covers these two CVEs only.
  • Restart after upgrading. Xint says a reload does not replace the running NGINX binary, so restart or do a live binary upgrade.
  • Front-end termination may help. Wiz says a CDN or WAF that terminates HTTP/2 before NGINX may partly reduce the risk. Treat it as partial.

What to look for in logs

F5 has published no indicators of compromise. The signs below come from Wiz and Xint. Both describe them as general warning signs and do not treat them as confirmed indicators.

  • Unexpected NGINX worker crashes, such as segmentation faults in the error log, per Wiz and Xint.
  • Commands or processes launched by the NGINX worker account, per Wiz. Xint suggests auditd to record what workers execute.

FAQ

Am I exposed to CVE-2026-123007 or CVE-2026-123633?

You are if an NGINX server has HTTP/2 on, runs a build without the fix, and untrusted clients can reach it. CVE-2026-123633 also needs NGINX to be proxying to a backend.

Are they being exploited?

No exploitation has been reported, and neither is on CISA KEV. Rapid7 published proof-of-concept code for CVE-2026-123007 on November 18. Wiz and Xint say they showed remote code execution but have not released their exploits.

Why do the scores differ?

F5 gives both 8.1 High on CVSS 3.1 and 9.2 Critical on CVSS 4.0. Both versions rate the attack as hard to pull off. The research results on official builds are why we cover it.

Where do I get the fixed version?

nginx.org released 1.30.7 (stable) and 1.31.9 (mainline) on November 18, 2026. If your NGINX comes from a distribution package, Ubuntu and Debian have not shipped fixed packages yet. Until you can upgrade, turn off HTTP/2 on affected listeners, per Wiz and Xint. F5 lists no workaround of its own.

Are F5's other NGINX advisories from the same day covered here?

No. F5 also published CVE-2026-123634 (resolver), CVE-2026-121810 (HTTP/3) and CVE-2026-113425 (mail proxy), and nginx.org fixed CVE-2026-125283 (try_files with alias, rated minor by nginx) in the same releases. Each needs a non-default feature, and turning off HTTP/2 does not help with them, per Xint.

Vendor
F5 (NGINX)
Product
NGINX Open Source and NGINX Plus, HTTP/2 module
Affected versions
CVE-2026-123007: NGINX Open Source 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8; NGINX Plus R33 and later before 37.0.8.1 and 37.3.0.1. CVE-2026-123633: NGINX Open Source 1.19.7 through 1.30.6 and 1.31.0 through 1.31.8; NGINX Plus R33 and later before 37.0.7.1 and 37.2.0.1. Per F5's CVE records. F5 says BIG-IP and F5OS are not affected
Vulnerable component
ngx_http_v2_module, on any listener with HTTP/2 turned on
CVSS
8.1 High (F5 as CNA, CVSS 3.1, attack complexity High) for both CVEs. F5 also gives 9.2 Critical on CVSS 4.0. nginx.org rates CVE-2026-123007 major and CVE-2026-123633 medium. NVD has not added its own score
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (F5, both CVEs)
CWE
CWE-191 and CWE-787 for CVE-2026-123007; CWE-416 for CVE-2026-123633 (F5)
Exploitation
Not observed
CISA KEV added
Patch
NGINX Open Source 1.30.7 or 1.31.9, released November 18, 2026. NGINX Plus 37.0.8.1 or 37.3.0.1, which cover both CVEs; NGINX Plus R33 through R36 get no fix of their own and need to move to one of those builds. Older Open Source branches also get no fix of their own and need to move to 1.30.7 or 1.31.9. Distribution packages keep their own version numbers, so check your distribution's advisory

Updates

Nov 18, 2026, afternoon. nginx.org released NGINX Open Source 1.30.7 and 1.31.9. Rapid7 published proof-of-concept code for CVE-2026-123007. Ubuntu and Debian have not shipped fixed packages. Still not on CISA KEV.

Nov 18, 2026. First published. F5 disclosed CVE-2026-123007 and CVE-2026-123633 and named the fixed releases; Wiz and Xint published research the same day. No exploitation reported; not on CISA KEV.

Sources

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

We publish an advisory when a vulnerability is Critical or on CISA KEV, has one identifiable component to check, and has a public proof of concept or reported exploitation. Advisories are updated as exploitation status changes.