TechAILatest.newsTrackers
Cybersecurity / AI security tools

NGINX patches NGINX2Root, five memory flaws that Xint says its AI found in 90 minutes

NGINX 1.31.9 and 1.30.7 fix NGINX2Root, five memory flaws including HTTP/2 bug CVE-2026-123007. Xint says AI found most of them; a public exploit exists.

By Emre A.Published

Abstract illustration of a shield over a networkTech AI Latest
Illustration of a shield over a network, made by Tech AI Latest for this story. Illustration: Tech AI Latest (Original illustration)

NGINX released versions 1.31.9 and 1.30.7 on 18 November 2026 to fix NGINX2Root, five memory corruption flaws that F5 rates 9.2 under CVSS 4.0. The worst, CVE-2026-123007, is an HTTP/2 flow control overflow present since 2015. Security firm Xint says its AI system found most of the flaws. Rapid7 has published a working exploit for a lab setup. No attacks in the wild had been confirmed as of 19 November.

Key facts

  • Released: 18 November 2026, NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable) (NGINX changelog)
  • NGINX2Root CVEs: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425, each 9.2 under CVSS 4.0 in F5's table, according to Sophos and Tenable
  • Worst flaw: CVE-2026-123007, an HTTP/2 flow control window overflow in code that dates to HTTP/2 support in version 1.9.5 (2015)
  • Credit: the changelog thanks Xint.io for four of the five flaws and Albert of Vexera AI for CVE-2026-123633; Wiz, Rapid7, Ikotas Labs and Metnir reported the HTTP/2 bugs independently
  • Exploit: Rapid7 published a proof of concept that runs code on NGINX 1.31.8 in a fresh Docker container
  • Exploitation: none confirmed in the wild and not in CISA's Known Exploited Vulnerabilities catalog as of 19 November, according to Mallory

What NGINX fixed

The NGINX project shipped mainline version 1.31.9 and stable version 1.30.7 on 18 November 2026. The official changelog lists ten security fixes in 1.31.9. Five of them make up the set that the security firm Xint, the research arm of Theori, named NGINX2Root. F5, which develops NGINX, published an out-of-band security notification, K000164058, covering the five CVEs on the same day.

The headline bug is CVE-2026-123007. The changelog describes it as a flow control window overflow in HTTP/2 that might let an attacker crash a worker process "or might have potential other impact". Xint traces it to an accounting error that pushes the connection window past its 31-bit limit. The vulnerable code arrived with the HTTP/2 module in NGINX 1.9.5, released in September 2015, so every release from then until 1.31.8 is affected. The other four are use-after-free bugs: one in HTTP/2 and one in HTTP/3 when worker_connections run out, one in the resolver directive when the same name is resolved in parallel subrequests, and one in the mail proxy server.

F5 rates all five 9.2, Critical, under CVSS 4.0, according to write-ups by Sophos and Tenable. Bitsight notes that F5's CVE record gives CVE-2026-123007 a CVSS 3.1 score of 8.1, High. F5 says code execution requires address space layout randomization (ASLR) to be disabled or bypassed, as quoted by Sophos.

How AI found the bugs

The NGINX changelog thanks Xint.io for four of the flaws: CVE-2026-123007, the HTTP/3 use-after-free, the resolver bug and the mail proxy bug, the last jointly with Maxim Dounin. It credits the HTTP/2 use-after-free, CVE-2026-123633, to Albert of Vexera AI. Xint says, as reported by iTnews, that it found CVE-2026-123007 while preparing for the ZeroDay Cloud 2026 contest and that its automated system then read about 50,000 lines of NGINX source in 90 minutes and returned four flaws without human guidance. Those figures are Xint's own and have not been checked independently.

Xint was not alone. Wiz Research, Rapid7, Ikotas Labs and Metnir reported the same HTTP/2 bugs to F5 independently, according to Tenable and Mallory. Ikotas Labs published its finding under a different name, NGINX2Shell. Several teams finding one decade-old bug in the same weeks fits a pattern this site has tracked all month: Oracle's Java4Shell fix on 17 November credited a researcher who used OpenAI's Codex, and the Xen project patched grant copy flaws found by Claude. Our comparison of AI bug hunting programs explains why defenders now see more critical reports in older C code.

Who is exposed and how to fix it

Any server running NGINX Open Source from 1.30.0 to 1.30.6 or from 1.31.0 to 1.31.8 should move to 1.30.7 or 1.31.9, or to a distribution package that backports the fixes. The HTTP/2 flaw needs only HTTP/2 enabled on a listener, which is a common setup in front of web apps and AI inference APIs. Outlets differ on the exact fixed NGINX Plus builds, so Plus customers should check F5's notification directly.

Where an upgrade has to wait, Wiz and Xint suggest turning off HTTP/2 on exposed listeners, according to Sophos. That blocks only the two HTTP/2 bugs and breaks native gRPC proxying. F5 also advises avoiding the SSI and mirror directives and proxied server names that use variables, and limiting mail proxy listeners to trusted networks.

Rapid7 published a proof of concept on 18 November that achieves unauthenticated code execution against NGINX 1.31.8 in a freshly started Docker container. Rapid7 warns that it will likely fail against busy servers, servers with a used heap, or traffic that passes through a proxy. Code runs as the NGINX worker user. To reach root, Xint chained the HTTP/2 bug with a separate use-after-free in the Linux kernel's SCTP networking code and escaped a Docker container in testing; that kernel bug had no CVE or patch as of 19 November, according to iTnews and Mallory.

What to watch next

No exploitation in the wild had been confirmed, and the flaws were not in CISA's Known Exploited Vulnerabilities catalog as of 19 November, according to Mallory. A public exploit usually shortens that window. The open questions are when Linux maintainers ship a fix for the SCTP bug that turns a worker compromise into root, and how many older NGINX builds bundled inside appliances and containers will never receive the patch. PHP shipped its own emergency fix on 19 November for a session flaw that the security firm depthfirst says its AI platform found, so administrators of common web stacks face several AI-found critical bugs in one week. Follow our cybersecurity coverage for updates.

What changed

BeforeNGINX 1.31.8 and 1.30.6 and every release back to 1.9.5 carried an HTTP/2 flow control overflow and four memory bugs, with no fix available
AfterNGINX 1.31.9 and 1.30.7 fix all five NGINX2Root flaws; a public proof of concept from Rapid7 exists
Who it affectsOperators of NGINX web servers, reverse proxies and mail proxies, especially those with HTTP/2 or HTTP/3 enabled; NGINX Plus customers

Questions people ask

What is NGINX2Root?
NGINX2Root is the name Xint gave to five memory corruption flaws in NGINX, led by CVE-2026-123007, an HTTP/2 flow control overflow. F5 rates each 9.2 under CVSS 4.0.
Which NGINX version fixes NGINX2Root?
NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable), released on 18 November 2026, fix all five flaws, according to the NGINX changelog.
Is NGINX2Root being exploited?
No attacks in the wild had been confirmed as of 19 November 2026, but Rapid7 has published a working proof of concept for a lab setup.
Did AI find the NGINX flaws?
Xint says its automated AI system found four of the flaws in about 90 minutes. Several human-led teams, including Wiz and Rapid7, found the HTTP/2 bugs independently.

Sources

  1. nginx changes (1.31.9 and 1.30.7) (NGINX, 18 Nov 2026)
  2. CVE-2026-123007 proof of concept (Rapid7, 18 Nov 2026)
  3. Patches released for critical NGINX2Root vulnerabilities (Sophos, 18 Nov 2026)
  4. NGINX2Root FAQ: Five vulnerabilities in NGINX (CVE-2026-123007) (Tenable, 19 Nov 2026)
  5. Nginx servers rootable through critical flaws, unpatched Linux kernel bug (iTnews, 19 Nov 2026)
  6. NGINX2Root CVE-2026-123007 rapid response (Mallory, 19 Nov 2026)
  7. NGINX2Root: Exposure details and fixes for all 5 nginx CVEs (Bitsight, 19 Nov 2026)

Reference pages

Spotted an error? See the corrections policy and tell the editor. Facts in this story come from the sources listed above; vendor claims are attributed.

Comments

Loading comments.

No links, no insults; comments that break the rules are not published. 0/1000

Related stories

All cybersecurity