On this page
What is the NGINX HTTP/2 vulnerability and which versions fix it?
Two serious HTTP/2 flaws in NGINX, CVE-2026-123007 and CVE-2026-123633, were publicly disclosed on 18 November 2026. Both can be reached without logging in and both need HTTP/2 enabled. NGINX 1.30.7 (stable) and 1.31.9 (mainline) fix them, and NGINX Plus has its own fixed releases. If you cannot upgrade, disable HTTP/2.
According to Wiz, the disclosure was coordinated with an F5 security release, the pair can lead to remote code execution, and both are scored 9.2 (Critical) on the CVSS 4.0 scale. The nginx.org release notice confirms that the two new versions were released on 18 November 2026 and carry fixes for ten CVEs in total.
What are CVE-2026-123007 and CVE-2026-123633?
- CVE-2026-123007 is an integer underflow (CWE-191) in HTTP/2 handling, according to Rapid7. The nginx.org advisories page describes it as memory corruption in HTTP/2 flow control.
- CVE-2026-123633 is a use-after-free in HTTP/2. Security firm Xint says it applies where HTTP/2 is combined with upstream proxying.
The researchers at Xint call their write-up of the first flaw "nginx2root". We are not describing how any exploit works. The point for administrators is simpler: these are memory-safety bugs in a component that faces the internet.
Who found them?
Wiz says the issues were found independently by several teams, including Wiz Research, Rapid7 and Xint, and reported to F5. Rapid7 credits Stephen Fewer, a senior principal security researcher, with CVE-2026-123007. Xint says one of its researchers found that flaw while preparing for the ZeroDay Cloud 2026 contest.
How long had the flaw been there?
The nginx.org advisories list CVE-2026-123007 as present from version 1.9.5 and CVE-2026-123633 from 1.19.7, both through 1.31.8. That is the basis for the "10-year-old" framing in some headlines, although we could not open The Hacker News article to check its wording.
Which versions are affected and fixed?
| Product | Affected | Fixed |
|---|---|---|
| NGINX Open Source, stable | 1.9.5 to 1.30.6 (CVE-2026-123007); 1.19.7 to 1.30.6 (CVE-2026-123633) | 1.30.7 |
| NGINX Open Source, mainline | 1.31.0 to 1.31.8 | 1.31.9 |
| NGINX Plus (CVE-2026-123007) | 37.0.0 to 37.0.7.1; 37.1.0 to 37.2.0.1 | 37.0.8.1; 37.3.0.1 |
| NGINX Plus (CVE-2026-123633) | R33 and 37.0.0 onward, per Wiz | 37.0.7.1; 37.2.0.1, per Wiz |
The NGINX Plus rows come from Rapid7 and Wiz rather than from F5's own advisory, which we could not load because the F5 support site returned only an error page. The two vendors also differ on older Plus releases. Wiz lists R33 as the first affected release, while Rapid7's table shows R34 to R36 with no fixed version listed. If you run an older Plus release, check F5's advisories directly. nginx.org links them as K000163926 for CVE-2026-123007 and K000163928 for CVE-2026-123633.
Distribution packages are a separate question. Xint warns that distributions may backport fixes without changing the version printed by the nginx version command, so compare the full package version with your distribution's own advisory. We have not confirmed any distribution's status.
How serious is it?
The sources do not fully agree. Wiz and Rapid7 give CVE-2026-123007 a CVSS 4.0 score of 9.2 (Critical), and Wiz gives the same score to CVE-2026-123633. The nginx.org page labels the first "Major" and the second "Medium", which uses the project's own scale rather than CVSS.
Neither Wiz nor Rapid7 reports exploitation in the wild. Wiz says its researchers built proof-of-concept exploits in a lab but are withholding them, and that exploitation is difficult in practice. Rapid7's CVSS vector includes a high attack-complexity rating, which fits that description.
What should administrators do now?
- Upgrade to NGINX 1.30.7 or 1.31.9, or the fixed NGINX Plus release for your branch.
- Restart, not just reload. Xint advises restarting after the upgrade because a reload does not replace the running binary.
- If you cannot upgrade, disable HTTP/2. Wiz says that on NGINX 1.25.1 or later this means setting the http2 directive to off in affected server blocks and removing the http2 parameter from listen directives. Test your applications first, reload, and confirm old worker processes have exited. Xint notes that clients needing HTTP/2, such as native gRPC, will be affected.
- Check what else is exposed. The same release fixes eight other CVEs, including flaws in HTTP/3, the mail proxy and the resolver.
Analysis: why this one deserves a fast patch
This is our own reading, not a claim from the vendors. NGINX often sits at the edge of a network as a reverse proxy, load balancer or Kubernetes ingress, so a flaw reachable before authentication tends to matter more than its raw difficulty suggests. The researchers' point that attackers may focus on packaged builds with common configurations is a reason not to assume your setup is unusual enough to be safe.
It is also the second HTTP/2 web server flaw we have covered this month. Our report on the Apache HTTP Server critical HTTP/2 flaw fixed in 2.4.71 described a similar pattern: a widely deployed web server, a protocol feature many sites enable, and a patch that has to be applied by hand. If you run Java services behind NGINX, the Java4Shell OpenJDK Base64 flaw is another fixed-version check for the same maintenance window. And for teams managing remote access tooling, see what administrators should do about the ScreenConnect extension flaw.
Sources
FAQ
Frequently asked questions
Neither Wiz nor Rapid7 reports exploitation in the wild as of their 18 November 2026 posts. Wiz says it is withholding its proof-of-concept exploits. That could change, so patching promptly remains the safer course.
According to Wiz, both flaws require HTTP/2 to be enabled on the NGINX server. If no listener uses HTTP/2, these two CVEs do not apply, but the release also fixes other issues, so upgrading is still sensible.
Install 1.30.7 on the stable branch or 1.31.9 on the mainline branch, as listed by nginx.org. NGINX Plus customers should move to the fixed release for their branch and confirm it against F5's advisory.
Wiz and Xint both give disabling HTTP/2 as the workaround for these two CVEs, but it is a stopgap. It can break clients that need HTTP/2, and you should still upgrade.
Spotted an error? Tell us. Read how we report and correct stories in our editorial policy.
Written by
Mainstream Tech
Newsroom
News and analysis on technology, AI, business, politics and international affairs, from our newsroom in London.
More from Mainstream




