The official nginx security advisories page lists several newly addressed flaws that are marked as not vulnerable in nginx 1.31.9 and newer, and in the 1.30.7 and newer updates on the stable line. Two of the most serious involve HTTP/2, the protocol many websites use to talk to browsers more efficiently than older HTTP.
One is CVE-2026-123007, described as “Memory corruption in HTTP/2 flow control,” and rated major. Nginx says versions 1.9.5 through 1.31.8 are vulnerable, and that 1.31.9 and newer, and 1.30.7 and newer, are not. Memory corruption means a bug can make a program handle memory the wrong way, which can crash the program and, in some cases, be turned into a more serious attack. This official list does not, by itself, say whether anyone has exploited the bug in the wild.
A second HTTP/2 issue, CVE-2026-123633, is described as a “Use-after-free in HTTP/2” and rated medium. A use-after-free is a programming error in which software keeps using memory after it should have stopped. Nginx lists versions 1.19.7 through 1.31.8 as vulnerable, with the same fixed releases as above. The advisories page also lists other recent issues, including problems in related networking features, that share those fixed versions.
A Docker blog post dated November 19 said OpenJDK and Oracle disclosed Java4Shell on November 17, “and NGINX released fixes for two HTTP/2 flaws the next day.” Docker said it rebuilt its hardened nginx images on versions 1.30.7 and 1.31.9 and told users to install the updated image and put it into service. That post is useful for dating the HTTP/2 fixes to November 18, and it matches the version numbers on nginx’s own advisory list.
Nginx is popular software for serving websites and routing traffic, including on school and small-business servers as well as large platforms. Site owners do not usually install it on a phone, but if a school, club, or company runs a website on nginx, the people who maintain that server are the ones who need to update it. Official advice from the vendor is to move to a release that is listed as “not vulnerable.”
This article does not include attack details. For operators, the checklist is short: check the running nginx version, upgrade to 1.30.7 or 1.31.9 or later, and restart the service so the new code is actually in use.