Thursday, November 19, 2026 Updated Briefings Saved 中文
AI Daily Radar

AI and the frontier tech around it, explained every morning

Demonstrated

Wiz reports pre-auth RCE in nginx HTTP/2 handling

Photo: kewl / Pixabay

Wiz published research describing pre-authentication remote code execution (RCE) flaws in nginx’s HTTP/2 handling — a class of bug that can let an attacker run code on a web server without logging in first. The same flaws are separately claimed by Xint, a Darpa-backed security company that told Forbes its AI models, GPT 6.1 Sol and GPT-6 Luna, found RCE vulnerabilities in nginx; Wiz says it had independently found the same bugs. The write-up is a research blog, not an official nginx advisory, and no evidence of active exploitation was presented. Commenters noted that a fix appears to have landed in nginx’s open-source repository roughly a week before the disclosure, with a commit crediting “Reported by Xint.io” but no public notice telling operators to disable HTTP/2 in the meantime.

Verified and unconfirmed

  • Verified: Wiz’s research post describes pre-authentication remote code execution vulnerabilities in nginx’s HTTP/2 handling; Forbes reported that Xint says its AI models found RCE flaws in nginx and that Wiz says it separately found the same flaws. Cybersecurity News reported that both flaws carry a CVSS 4.0 score of 9.2 and named Ikotas Labs, Metnir, Rapid7 and Xint as independent finders across the two disclosures.
  • Not yet confirmed: The supplied evidence contains no official nginx/F5 advisory, affected-version list or patch version; the claim that the fix is nginx 1.31.9 comes from a single outlet, and there is no evidence of active exploitation. Community comments that the bug was fixed in the open-source repository a week before disclosure, with a commit crediting Xint, remain unverified.

Background

HTTP/2 support — which lets a single connection carry many multiplexed requests — has shipped in nginx since version 1.9.5 in 2015, so the affected code path exists in more than a decade of releases. Wiz’s write-up and Xint’s separate “nginx2root” publication describe overlapping findings: Wiz says both of its flaws require HTTP/2 to be enabled, while Xint says disabling HTTP/2 on affected listening ports blocks CVE-2026-123007 and CVE-2026-123633 but not the three other nginx flaws it lists, one of which it chains with a kernel exploit to reach root on the host. Forbes reports that Xint credits the GPT 6.1 Sol and GPT-6 Luna models for its discovery, and that Wiz says it found the same flaws independently.

Why it matters

Anyone running nginx with HTTP/2 enabled has a concrete decision to make: apply the upstream fix or turn HTTP/2 off, a workaround commenters described as simple and one that argues for a faster public warning. The reported gap between the public fix commit and the write-up also matters for operators, because it gave anyone watching the repository a window to study a pre-auth RCE before defenders were told to act.

What to watch

Whether nginx’s maintainers or F5 publish an official advisory with CVE identifiers and the affected version ranges, which would let operators confirm whether their builds are exposed.

Community discussion

The strongest argument in the thread, from black3r, is about disclosure timing: the fix was reportedly visible in the open-source repo about a week earlier, so skilled attackers could have mined it, and a bare notice to disable HTTP/2 would have cost little. Other commenters reacted to the AI angle — one worried about the volume of vulnerable small servers — while hokkos flagged a separate oddity, an empty SHA-256 digest on the nginx 1.31.9-alpine Docker image, which is an observation about that image rather than a stated link to the flaws.

Coverage of this story

Further reading

Comments

Comments

Comments use a GitHub account and are moderated. Comment rules

More in Industry & Policy

See all

Ruby2ßhell: reported pre-auth RCE in stock Rails

A public write-up dubbed Ruby2ßhell claims a pre-authentication remote code execution vulnerability in stock Ruby on Rails, tied to a single-byte overflow in ß case conversion....