NGINX's HTTP/2 flaw let attackers run code without logging in — and it hid in the code for a decade

Pre-auth RCE in Nginx HTTP/2 handling

Wiz Research and four other teams independently found two critical NGINX vulnerabilities, CVE-2026-123633 and CVE-2026-123007, both rated 9.2 and requiring only HTTP/2 to be enabled. The integer underflow dates back to NGINX 1.9.5 from 2015; the use-after-free lurked for nearly six years. Attackers can execute code on servers serving even plain static files, and AI tools helped surface both flaws. F5 released fixes on November 18.

Complexity can no longer be relied upon as a barrier to discovery or exploitation.
  1. Buttons840

    Everyone's worried about security right now, even non-tech people, but hasn't half the nation's personal data been leaked twice a month for the last decade or two?

    I know times are changing, it's just curious that nobody seemed to care until now.

  2. black3r

    The bug was apparently fixed in open source repo a week earlier, this could've been abused by anyone smart enough to monitor repos like this for exploitable bugfixes for a week (the commit message even included "Reported by Xint.io" and I'm guessing skilled black hats would know about Xint)

    Given that in this case the workaround is as simple as disabling http2, there is honestly no reason why F5/Nginx or any of the reporting teams couldn't at least put out a PSA to disable http2 for the time being before basically telling the whole wide world this exists and how to exploit it.

    Especially for software like Nginx which powers a huge part of the internet.

  3. fduran

    Small consolation but HTTP/2 is not enabled by default in Nginx and "only" 12% of servers run it (still huge at Internet scale) https://w3techs.com/technologies/segmentation/ce-http2/web_s...

  4. malikNF

    Hey so, does anyone know of a good tutorial on getting in to woodwork?

  5. hackthemack

    I notice a phenomena that when older software has a critical vulnerability, like say Apache, you get quite a few comments of "Why does anyone use that? Use Nginx"

    But when newer software has the same vulnerability, you do not see the same kind of comments.

    There always seems to be a latent stance in IT that newer is better.

  6. fn-mote

    AI is burning down the internet. This is insane.

    Are we going to discover in a year that every server online this month had a rootkit installed? There’s got to be thousands who are too small time to wipe and reinstall.

  7. pelzatessa

    If you want to check if your host might be vulnerable:

    https://xint.io/blog/nginx2root-remote-code-execution#23-com...

    Workarounds if you're vulnerable and can't update immediately:

    https://xint.io/blog/nginx2root-remote-code-execution#33-eme...

  8. TuckerBMorgan

    I wonder when all of this die down. I assume at some tipping point most software will be written/patched with LLMs and so hopefully (fingers crossed) more resistent to these bugs.

    Certainly a stressful time for sysadmins everywhere, let us hope your coworkers are picking up your beer tab

  9. nikcub

    every major exploit now comes with a marketing website - nginx2root dot com in this case

    the certificate for it was issued on the 2nd of November

    if you were scanning CT logs you would have had a 16 day head start on RE'ing this

    there are more examples in the current CT logs

    https://api.certspotter.com/v1/issuances?domain=nginx2root.c...

  10. ROllerozxa

    Well I guess this was the vuln that was teased about on Mastodon some hours ago:

    https://is-a.cat/@ar/117634569518544368

More from this day

2026-11-18