Nginx Fixes 10 Security Flaws, Two of Them in Its HTTP/2 Handling

The nginx project has released new stable and mainline versions of its web server, 1.30.7 and 1.31.9, with fixes for 10 security flaws. Its announcement is dated Nov. 18, 2026. Two of the flaws are in the way the server handles HTTP/2, one of the protocols a browser uses to request pages.
For anyone running nginx, the answer is the upgrade — the project lists all 10 flaws as fixed in 1.30.7 and 1.31.9, and lists affected releases going back a long way. One of the 10, a memory-handling flaw in the component that looks up host names, is recorded as present in every version from 0.6.18 to 1.31.8.
nginx rates the severity of each flaw itself. It puts memory corruption in HTTP/2 flow control (CVE-2026-123007) at major, and a second HTTP/2 flaw of the same memory-handling kind (CVE-2026-123633) at medium; the first is listed as present from 1.9.5 onward. The project's two other major ratings go to an infinite loop while reading a client request body over TLS 1.3, and to a flaw in the mail proxy module. The full list, with the affected versions for each flaw, is on the project's security advisories page.
Those ratings are the project's own. The researchers who reported the two HTTP/2 flaws have rated them more seriously than nginx does. The project's advisories go no higher than major, and neither of its pages mentions an attack using any of the 10.
nginx shipped a comparable set of fixes on Oct. 14, 2026, in versions 1.30.6 and 1.31.7, according to the same news page.
