deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

nginx HTTP/2 flaws rated 9.2 fixed upstream, but Ubuntu's stock package remains unpatched

Two HTTP/2 flaws in nginx, both rated 9.2 under CVSS 4.0, are fixed in 1.30.7 and 1.31.9 — but Ubuntu's archive still ships a vulnerable build and the official mitigation fails on it.

nginx HTTP/2 flaws rated 9.2 fixed upstream, but Ubuntu's stock package remains unpatched

Two critical vulnerabilities in nginx's HTTP/2 implementation were disclosed this week, reaching the top of Hacker News with over a thousand points, where the issue was described as an unauthenticated remote code execution flaw. According to a hands-on write-up on dev.to, the bugs were found by Wiz Research together with Ikotas Labs, Metnir, Rapid7 and Xint, and reported to F5, which maintains nginx. Both are rated 9.2 under CVSS 4.0.

Two flaws, one eleven years old

The first, CVE-2026-123633, is a use-after-free in HTTP/2 connection handling. It is easier to exploit when nginx runs as a proxy and its connection slots are running low. It affects the open-source server from 1.19.7 through 1.31.8.

The second, CVE-2026-123007, is an integer underflow in the HTTP/2 send_window accounting. Per the dev.to analysis, it is exploitable even on a default configuration serving static files, and it reaches back to version 1.9.5 — making the bug roughly eleven years old.

Both flaws require HTTP/2 to be enabled, but neither depends on a third-party module. The official fixes are nginx 1.30.7 (stable) and 1.31.9 (mainline).

Ubuntu's archive is still shipping vulnerable builds

The dev.to author tested what a plain apt-get install nginx yields on Ubuntu 24.04: version 1.24.0, which falls inside both vulnerable ranges. Ubuntu's security tracker pages, last updated on 18 November, listed every supported release — 24.04 LTS included — as vulnerable, with no fixed package version published for either CVE.

The upstream fix does exist outside Canonical's archive: nginx.org's own repository already carries 1.30.7 built specifically for Ubuntu 24.04 (noble). The author verified the package entry in the repository's index directly rather than taking that on faith.

Not every install is exposed

A completely untouched install is not at risk: the default site configuration listens on plain port 80, with no TLS and no HTTP/2 anywhere. Exposure begins the moment an operator adds a certificate and writes the listen 443 ssl http2 line — the standard, unremarkable step in nearly every TLS setup guide. Forgotten, unconfigured boxes are safe; boxes doing the normal thing are not.

The documented mitigation breaks on stock Ubuntu

For operators who cannot upgrade immediately, the advisory recommends setting http2 off; in the affected server block. That directive only exists since nginx 1.25.1, when HTTP/2 configuration was split out of the listen line. Ubuntu 24.04 ships 1.24.0, which predates the change by more than a year — so copying the advisory verbatim onto a stock Ubuntu box produces an unknown directive error and a configuration that refuses to load.

The working equivalent on 1.24.0 is to drop the http2 parameter from the listen line itself. The dev.to author confirmed the mitigation works there: a client requesting HTTP/2 against that server gets HTTP/1.1 back.

Disabling HTTP/2 is not free

Rather than guess at the cost, the write-up benchmarked the mitigation: 30 small static files of about 20KB each served over TLS, 900 requests per run, three runs each, on loopback.

  • HTTP/2 over a single connection: 19.6–20.3 ms, roughly 44,400–46,000 requests per second
  • HTTP/1.1 over six connections (the typical browser limit): 28.5–34.3 ms, 26,300–31,600 requests per second
  • HTTP/1.1 over a single connection: 66.9–78.2 ms, 11,500–13,500 requests per second

Browser-like traffic recovers most of the gap by opening more connections, landing 45–70% slower — not catastrophic. Workloads that reuse one persistent connection, common for service-to-service calls and some mobile and IoT HTTP stacks, take a 3.4x to 3.9x hit instead. And because the test ran on loopback, real-world numbers will be worse: every extra HTTP/1.1 connection costs a full TLS handshake over actual network latency.

A free signal for scanners

Ubuntu's default configuration leaves server_tokens on, so every response advertises the exact build, such as nginx/1.24.0 (Ubuntu). Combined with a publicly documented vulnerable version range, that hands anyone scanning for targets a free signal. Turning it off — one commented-out line in /etc/nginx/nginx.conf — fixes neither CVE, but stops the server advertising which bug it might carry, at no cost.

Why it matters

nginx fronts an enormous share of the web, and this incident exposes the gap between an upstream advisory and deployable reality. The patched releases exist, yet the default install path on a major LTS distribution still delivers a vulnerable build with no published fix date, and the official mitigation syntax fails on that same build. Operators on distro packages must either wait for backports, switch to nginx.org's repository, or hand-edit the listen directive while weighing a measurable performance penalty against staying exposed. The eleven-year-old integer underflow is also a reminder of how long latent bugs can sit in core internet infrastructure without anyone looking closely.

  • #nginx
  • #security
  • #http2
  • #ubuntu
  • #vulnerability

Related posts