Skip to content

Nginx patches an HTTP/2 bug that has been there since 2015

CVE-2026-123007 is a major-severity memory corruption bug in HTTP/2 flow control, present in every release back to 1.9.5. A second, newer use-after-free is fixed in the same update.

Source: Nginx

Nginx’s security advisories page lists fixes for two HTTP/2 bugs today, both closed in 1.30.7 (stable) and 1.31.9 (mainline). CVE-2026-123007, rated major severity, is memory corruption in HTTP/2 flow control, and it has been present in every release since 1.9.5 in 2015. CVE-2026-123633, rated medium, is a use-after-free that only affects reverse-proxy configurations and was introduced later, in 1.19.7.

Security researchers at Wiz, who helped find the flaws, describe CVE-2026-123007 as capable of unauthenticated remote code execution and rate it 9.2 on CVSS, a higher bar than Nginx’s own “major” label. Both bugs require HTTP/2 to be enabled on the server, which it is by default on most modern configurations. The fixes went through a coordinated disclosure process with F5, which now owns Nginx.

nginx -v
# anything from 1.9.5 up to 1.31.8 needs the update

Why it matters: Nginx sits in front of a huge share of the web, and an eleven-year-old bug in a protocol most sites have had switched on for years is as close to “check this today” as this beat gets. Confirm your version, and don’t wait for a distro package to catch up if you built nginx from source.

The caveat: Nginx has not confirmed exploitation in the wild, and its own severity rating for the RCE-capable bug is more measured than Wiz’s.

Share

Related reading

More from The Wire

All briefs