Your application can be correct and still lose. The process that accepts the socket is the one that has to be patched.
F5's November 18, 2026 nginx release includes fixes for two critical HTTP/2 bugs that need no login.
nginx terminates TLS and parses the request before your code runs. If that process is compromised, you are already on the box with the certificates and the backends.
A clean handler does not get a vote.
Wiz got code execution from CVE-2026-123007 on official nginx 1.31.7 and 1.31.8. That path was HTTP/2 over TLS on 64-bit builds, and ordinary static files reach it with no backend and no extra module.
The other bug, CVE-2026-123633, is the reverse-proxy path. It shows up when free connection slots run low.
Both live in nginx, and both need HTTP/2 on. Neither needs a mistake in the site behind them.
The static-file bug has been there since nginx 1.9.5, in 2015. Ten years in production is a calendar entry, not a review.
Several labs reported these in the same disclosure. The parser did not get safer by staying up.
Open source is fixed in 1.30.7 stable and 1.31.9 mainline. Plus builds differ per CVE, so use the advisory table instead of rounding a version in your head.
A package named nginx is a version number. Read it.
Stuck tonight? Turn HTTP/2 off until the fixed binary is the one serving traffic. On 1.25.1 or later, set http2 off; in the affected server blocks and remove the http2 parameter from every listen line.
Reload, confirm the old workers have exited, then upgrade. Turn HTTP/2 back on only after that binary is serving.
A CDN or a WAF might blunt part of this only if it terminates HTTP/2 and does not pass that connection through to nginx. Wiz says it depends on the implementation.
Check the hop in front of you.
- Do not grep your app for the CVE and close the ticket.
- Do not leave HTTP/2 on while the upgrade sits in a test queue.
- Do not treat a long-lived worker as proof the parser is fine.
- Do not shrug off a worker crash, or a command nginx itself started. Those are warnings, not a confirmed hit.
- Do not assume one nginx means one site.
Takeaway: patch the process that accepts the connection, or turn off the protocol the bug requires.
This post was generated automatically from public Hacker News data.

