Ubuntu Patches nginx Flaws in 8 Releases: Update Now

Share

The short version: Canonical published the nginx Ubuntu security update, USN-9159-1, on 19 November 2026, fixing eight vulnerabilities across Ubuntu 14.04 LTS to 26.10. Two are rated High, both in HTTP/2: a memory corruption bug and a use-after-free that can crash a worker process and, in narrower cases, run code. Ubuntu 22.04, 24.04, 26.04 and 26.10 have the fixes in the normal archive; 20.04 and older need Ubuntu Pro. Updating is a standard apt upgrade and a service restart.

KEY TAKEAWAYS

1Eight CVEs: USN-9159-1 covers nginx on every maintained Ubuntu release, from 26.10 back to 14.04.
2Two are High: CVE-2026-123007 and CVE-2026-123633 live in HTTP/2 and can lead to code execution when ASLR is off or bypassed.
3Newer releases get it free: 22.04, 24.04, 26.04 and 26.10 receive the fix through a normal upgrade. 20.04 and older need Ubuntu Pro, and 16.04 and 14.04 need its Legacy Support add-on.
4Check the package, not the banner: nginx -v prints the upstream base version, so use apt policy nginx to see the Ubuntu revision you actually have.
5nginx.org users are separate: if you installed from nginx.org rather than Ubuntu, the fixed upstream releases are 1.30.7 and 1.31.9.

What USN-9159-1 fixes

Canonical lists the affected releases for each fix, and they differ: the HTTP/2 and HTTP/3 bugs only exist where those protocols are enabled, while two use-after-free bugs reach every release listed.

CVE The flaw Releases named in the notice
CVE-2026-123007 Memory corruption in HTTP/2 flow control 16.04 to 26.10
CVE-2026-123633 Use-after-free in HTTP/2 when proxying 16.04 to 26.10
CVE-2026-113425 Use-after-free in the mail proxy module All eight releases
CVE-2026-123634 Use-after-free while resolving names All eight releases
CVE-2026-118899 Infinite loop reading a request body over TLS 1.3 24.04, 26.04, 26.10
CVE-2026-120967 SNI bypass of client certificate checks in stream 26.04, 26.10
CVE-2026-121810 Use-after-free in HTTP/3 26.04, 26.10
CVE-2026-123640 Information leak while parsing ClientHello messages 26.04, 26.10

Two entries depend on features you may not use. nginx.org lists 1.25.5 as the first version affected by the client certificate bypass, so 24.04 and older are clear. The HTTP/3 bug needs an HTTP/3 listener. On 14.04, only the mail proxy and resolver fixes apply; neither HTTP/2 bug reaches that release.

The two HTTP/2 flaws are the ones to act on

CVE-2026-123007 is a heap buffer overflow in HTTP/2 flow control. Canonical’s description says an attacker can push the flow control window past its limit with crafted traffic, corrupting memory in a worker process. The usual outcome is a segmentation fault; code execution becomes possible where ASLR is disabled or can be bypassed. Ubuntu’s tracker gives it 8.1 High on CVSS 3.1 and 9.2 Critical on CVSS 4.0, and marks it High priority with the note “this is an RCE”. The notice credits Stephen Fewer and Tomer Schwartz with the discovery.

CVE-2026-123633 is a use-after-free in the same HTTP/2 path, triggered when nginx proxies client requests to a backend and a worker is low on worker_connections. Ubuntu rates it 8.1 High as well, while nginx.org rates the same bug medium upstream. Canonical’s tracker scores it for possible code execution, while nginx.org rates the more likely outcome, a crashed worker. Canonical credits Albert Ebb Metnir and Nir Ohfeld in the notice.

Both bugs sit in the data plane and need HTTP/2 enabled on a listening server to be reachable. An HTTP/1.1-only site is not exposed to these two, but the same update still carries six more fixes, including the mail proxy use-after-free that nginx.org rates major. Upstream, nginx’s advisory list puts the fixed releases at 1.30.7 and 1.31.9, and names every version from 1.9.5 to 1.31.8 as vulnerable to the flow control bug.

To see whether either bug can reach your server, search the configuration nginx actually loads. No output, or only lines starting with #, means HTTP/2 is off.

CHECK WHETHER HTTP/2 IS ON
sudo nginx -T 2>/dev/null | grep -n http2

Fixed versions for each Ubuntu release

These are the package versions Canonical lists in USN-9159-1. On 22.04 and newer they come from the normal security archive. The +esm suffix means the fix is only for Ubuntu Pro subscribers, and 16.04 and 14.04 also need the Legacy Support add-on.

Ubuntu release Fixed nginx package Where it comes from
26.10 1.30.4-7ubuntu1.2 Standard archive
26.04 LTS 1.28.3-2ubuntu1.13 Standard archive
24.04 LTS 1.24.0-2ubuntu7.20 Standard archive
22.04 LTS 1.18.0-6ubuntu14.23 Standard archive
20.04 LTS 1.18.0-0ubuntu1.7+esm5 Ubuntu Pro
18.04 LTS 1.14.0-0ubuntu1.11+esm6 Ubuntu Pro
16.04 LTS 1.10.3-0ubuntu0.16.04.5+esm11 Pro with Legacy add-on
14.04 LTS 1.4.6-1ubuntu3.9+esm10 Pro with Legacy add-on

If your nginx came from the nginx.org repository rather than Ubuntu, none of these packages apply. The fixed upstream releases are 1.30.7 and 1.31.9, and every affected range on the advisory list ends at 1.31.8. Check the repository you actually use with apt policy nginx before updating.

How to update nginx on Ubuntu

Start by refreshing the package lists, then install the newer package. The upgrade only replaces nginx; it does not touch your site configuration.

REFRESH PACKAGE LISTS
sudo apt update
INSTALL THE NGINX UPDATE
sudo apt install --only-upgrade nginx

Then confirm the installed version matches the fixed revision for your release. nginx -v alone reports the upstream base version, such as 1.24.0, not the Ubuntu revision after the dash.

SHOW INSTALLED AND AVAILABLE VERSIONS
apt policy nginx

The upgrade usually reloads nginx by itself. Testing and restarting makes sure the workers run the new binary, and catches a broken config before it takes the site down.

TEST THE CONFIG AND RESTART
sudo nginx -t && sudo systemctl restart nginx

On 20.04 and older, confirm that the Pro service is attached and esm-infra is enabled before you expect the fixed package. The command pro status shows both. If you run nginx in containers, rebuild the image from the updated package or move to a fixed upstream tag; updating the host does not change an existing image.

If you are setting up nginx from scratch, our LEMP install guide covers the Ubuntu packages, and the APT flaw walkthrough explains how Ubuntu security updates reach your system.

Source: Ubuntu Security Notice USN-9159-1.