On November 19, I checked eight servers after NGINX disclosed six vulnerabilities. One web server met two conditions for CVE-2026-123007. NGINX accepted HTTP/2, and the installed Ubuntu package lacked the fix. Assessing the other findings meant checking the configuration and where each package came from. NGINX security advisories

What the six CVEs affect

CVEVulnerabilityWhat to check
CVE-2026-123007Memory corruption in HTTP/2 flow controlWhether NGINX itself accepts HTTP/2
CVE-2026-123633HTTP/2 use-after-freeWhether NGINX accepts HTTP/2 and proxies requests to a backend. The advisory also specifies a worker running short of connections
CVE-2026-118899Denial of service caused by a worker stuck in a loopWhether NGINX accepts HTTPS over TLS 1.3 and whether the particular build is affected
CVE-2026-123634Use-after-free in the built-in DNS resolverWhether a backend hostname contains variables and an SSI or mirror subrequest resolves that same name
CVE-2026-121810HTTP/3 use-after-freeWhether NGINX accepts HTTP/3
CVE-2026-113425Mail proxy use-after-freeWhether NGINX is configured as a mail proxy

For the five memory flaws, F5 lists possible remote code execution with the privileges of an NGINX worker if ASLR is disabled or can be bypassed. The reported impact of CVE-2026-118899 is denial of service. NGINX security advisories

What the server check found

I checked installed packages, running processes and listening sockets, then reviewed NGINX configuration on the hosts and inside containers. Several containers used versions below the fixed releases, but their NGINX listeners accepted plain HTTP. Where containers had a DNS resolver configured, I found none of the subrequests required for CVE-2026-123634.

The full Ubuntu package version mattered. The web server ran 1.18.0-6ubuntu14.22, and Canonical shipped the fix for Ubuntu 22.04 in 1.18.0-6ubuntu14.23. Canonical also specifies that CVE-2026-123633 affects cleartext HTTP/2 on this Ubuntu branch. The server used HTTP/2 over TLS, so CVE-2026-123007 was the applicable HTTP/2 finding. Ubuntu security notice · Canonical’s CVE-2026-123633 record

How I verified the update

After refreshing its indexes, APT still offered .22. The .23 packages were already available in the official Ubuntu archive, so I downloaded a matching set for NGINX and its installed modules. I checked the package versions and simulated the installation. APT planned to upgrade nine NGINX packages without adding or removing any packages.

After installation, nginx -t passed and the running service used the new binary. Two HTTPS sites returned HTTP/2 200 when checked directly from the host. That verified that the updated process was serving HTTP/2 traffic. I assessed CVE applicability from the advisories and configuration.

The NGINX project released fixes for all six CVEs in stable 1.30.7 and mainline 1.31.9. For distribution packages, check your distribution’s security notice. It may backport the fix to a branch with an earlier version number. NGINX security advisories · Ubuntu security notice

For a practical look at testing another proxy, see my article on adqproxy, built with Rust and Cloudflare Pingora. It covers first startup, routing, HTTPS, and upgrades that preserve configuration.