Incidents · NGINX / F5
NGINX HTTP/2 unauthenticated remote-code-execution flaws
Monitoring Last updated
Two critical NGINX HTTP/2 memory-safety vulnerabilities, CVE-2026-123633 and CVE-2026-123007, allow unauthenticated remote code execution in affected configurations. F5 coordinated fixes released November 18, with NGINX OSS 1.30.7 stable and 1.31.9 mainline listed as patched. Public research demonstrates exploitation in lab environments; widespread in-the-wild exploitation was not verified.
- Discovered
- ResolvedPending
- Permanent fix
- PostmortemPending
Timeline
What happened, in order
Wiz, Ikotas Labs, Metnir, Rapid7 and Xint coordinated disclosure of critical HTTP/2 RCE vulnerabilities, including successful lab exploitation. The issues were privately reported in October and November; public disclosure occurred November 18.
via Wiz disclosureF5 issued security fixes on November 18; NGINX OSS fixed versions include 1.30.7 and 1.31.9. Operators must deploy patches or temporarily disable HTTP/2. Production adoption and downstream recovery remain unverified.
via Wiz fixed-release matrix
Root cause
Confirmed cause
HTTP/2 connection reuse bookkeeping causes a use-after-free (CVE-2026-123633), while flow-control accounting and integer underflow can produce an out-of-bounds copy (CVE-2026-123007).
via Wiz technical disclosurePermanent fix
Shipped November 18, 2026
NGINX OSS 1.30.7 stable or 1.31.9 mainline address both vulnerabilities; relevant NGINX Plus patch levels are documented in the technical disclosure. Disabling HTTP/2 is a temporary mitigation, not a permanent fix.
Postmortems
None published yet
An official or independent postmortem will be linked here when one appears.