⌁AI·CYBER·BRIEF▌
Vulnerabilities6 min read

Five nginx flaws, three rated critical by F5: fixed in 1.30.6 and 1.31.7 — check your build and config

nginx 1.30.6 and 1.31.7 fix two heap overflows, a use-after-free, TLS session forgery and HTTP/3 body injection. Each needs a specific configuration. What to check.

nginx released versions 1.30.6 (stable) and 1.31.7 (mainline) on October 14, 2026, fixing five security vulnerabilities in one go — two heap buffer overflows, a use-after-free, a TLS session-forgery bug and an HTTP/3 request-injection bug. The nginx project rates all five as medium. F5, which owns nginx, scores three of them 9.2 out of 10 (CVSS v4.0), because they can corrupt memory in a worker process and, where address-space randomisation is disabled or bypassed, lead to code execution. F5 says it has found no evidence of exploitation. Every one of the five needs a particular configuration to be reachable, so the job today is twofold: confirm you're on a fixed build, and check whether your configuration was ever exposed.

What happened, in plain English

nginx is the web server and reverse proxy in front of a large share of the internet's sites, APIs and Kubernetes clusters. When it has a memory-safety bug, the blast radius is wide — but nginx is also extremely configurable, and most of its bugs only appear when certain features are combined.

That is the story of this batch. The nginx changelog and the project's advisories page list:

  • CVE-2026-15176 — a buffer overflow when the alias directive is used on a request URI that was changed by rewrite. Affects every version from 0.1.29.
  • CVE-2026-93479 — a buffer overflow while evaluating string expressions with variables, which affected the document root calculation and request logging. Affects only the recent lines: 1.31.2–1.31.6 and 1.30.0–1.30.5. Credited to Matt Suiche of Tolmo Inc.
  • CVE-2026-97205 — a use-after-free when asynchronous file I/O (AIO) is used with server-side includes that contain include virtual. Affects versions from 0.8.11.
  • CVE-2026-97629 — when TLS session-ticket key rotation is used, one key was left uninitialised, which "might allow to forge a session." Affects 1.23.2 onward.
  • CVE-2026-95101 — over HTTP/3, part of an unknown frame could be treated as the request body, bypassing client_max_body_size or injecting data into the proxied request. Affects 1.25.0 onward.

F5 classes the first three as critical. A heap overflow in a worker process is the kind of bug that crashes the worker at minimum; turning it into code execution is harder on a modern system with address-space layout randomisation (ASLR), which is why F5 adds that caveat.

Are you affected? What to do now

  • Check your version. nginx -v. Fixed: 1.30.6+ (stable) and 1.31.7+ (mainline; the current mainline is 1.31.8). Earlier versions are vulnerable to at least some of the five.
  • Check your distribution's package, not just the number. Most servers get nginx from Ubuntu, Debian, Red Hat or a container image, and distributions backport fixes without changing the upstream version. Look up the five CVE IDs in your vendor's security tracker (Ubuntu has published USN-8955-1, for example). Commercial NGINX Plus, NGINX Ingress Controller, NGINX Gateway Fabric and NGINX Instance Manager are covered by F5's own advisories.
  • Rebuild containers. An nginx image built before mid-October still carries the old binary. Pull the patched base image and redeploy — Kubernetes ingress controllers included.

Then check your configuration for the patterns each bug needs. These are worth looking at even after patching, to know whether you were exposed. The trigger conditions below are as described in F5's advisory, relayed on oss-security:

  • alias + rewrite + $request_filename (CVE-2026-15176): a location using alias, where rewrite changes the URI and a set or return directive references $request_filename.
  • map with regex captures used too early (CVE-2026-93479): a map whose regex capture variables are referenced before the map's output variable in a root directive or an access-log format.
  • aio + SSI include virtual (CVE-2026-97205): asynchronous file I/O turned on in a location that serves SSI pages with include virtual.
  • ssl_session_cache shared: without an explicit ssl_session_ticket_key (CVE-2026-97629): nginx's automatic ticket-key rotation. If you rely on TLS client certificates, this is the one to prioritise — F5 says a remote, unauthenticated attacker may be able to forge sessions and bypass client-certificate verification.
  • HTTP/3 with proxy_request_buffering on (CVE-2026-95101): listen ... quic plus proxying. F5 notes it is a data-plane issue only.

If you cannot upgrade immediately, steering away from the matching configuration closes the specific path: an explicit ssl_session_ticket_key file (or ssl_session_tickets off), aio off where SSI is served, removing the $request_filename reference, or temporarily disabling HTTP/3 listeners. Treat these as stopgaps; the upgrade is the fix.

Also on the list: njs 1.0.2, the nginx JavaScript module, released the same day with fixes for a memory-exhaustion bug in XML parsing (CVE-2026-101025) and inconsistent XML attribute values affecting signed-XML validation (CVE-2026-101019). And September's 1.30.5/1.31.6 fixed a separate HTTP/3 heap overflow with OpenSSL 3.5.0 and earlier (CVE-2026-90439) — included in the October builds.

The expert view

The gap between "medium" and "9.2" is not a contradiction so much as two ways of counting. The nginx project's severity reflects how few deployments hit the triggering configuration; F5's CVSS score describes what happens to a deployment that does. Both are useful, and the second is the one that matters for the subset of servers that match. The practical takeaway is that configuration review is part of the fix, not an optional extra — a version number alone tells you whether you're patched, not whether you were ever exposed.

Of the five, CVE-2026-97629 deserves more attention than its "session forgery" label suggests. TLS session tickets let a returning client skip the full handshake; if the server encrypts tickets with a key that was never properly initialised, an attacker can mint a ticket the server accepts. On a public website that mostly means skipping a handshake. On a service that authenticates clients with certificates — internal APIs, mutual-TLS gateways, B2B integrations — F5's warning is that the forged session may carry past client-certificate verification. That turns a cryptographic hygiene bug into an authentication bypass for exactly the deployments that chose certificates because they wanted stronger authentication.

The two heap overflows are the classic nginx risk pattern: complex interactions between directives that each work correctly alone. Code execution from a worker overflow on a modern 64-bit Linux build with ASLR is not trivial, and no public exploit had surfaced as of F5's advisory. But nginx is one of the most heavily targeted pieces of internet infrastructure — in May, researchers published a video proof-of-concept for a separate heap-corruption bug in nginx's rewrite engine, according to Orca Security — so "no known exploitation" five weeks after release is a reason to finish patching, not to stop.

Official sources

  • nginx security advisories — nginx project (affected and fixed versions per CVE, links to F5 articles)
  • nginx CHANGES — changelog for 1.31.7 (October 14, 2026) and 1.31.6 (September 15, 2026), with credits
  • nginx.org news — release announcements for 1.30.6, 1.31.7, 1.31.8 and njs 1.0.2
  • oss-security post — relaying F5 advisory K000163408 with per-CVE trigger conditions, October 23, 2026

Coverage: CSO Online (F5's CVSS 9.2 ratings, no exploitation found, affected F5 products), October 19, 2026; Orca Security (May 2026 rewrite-engine proof-of-concept).

Get the daily brief

AI + security signal by email: headlines, a two-line summary, a link. No noise, no spam.

How often