EST. 2026 — Notes from real server work SYSADMIN · SECURITY · AI · DIRECTADMIN Issue 01
THE SYSADMIN ALMANAC
Home / Security Update / Ubuntu nginx: CVE-2026-123007 Code Execution Risk, Patch Now
Security Update

Ubuntu nginx: CVE-2026-123007 Code Execution Risk, Patch Now

by Ton-Or ·19 Nov 2026·7 min read
Ubuntu nginx: CVE-2026-123007 Code Execution Risk, Patch Now

Administrators running internet-facing nginx should check their installation source and schedule urgent patching, prioritizing HTTP/2, HTTP/3, mail proxy, and stream services that verify client certificates.

1-minute summary

Symptom / problem
nginx มีข้อผิดพลาดด้านหน่วยความจำ การอ่าน TLS และการเลือกปลายทาง ซึ่งอาจทำให้บริการล่ม รันโค้ด หรือข้ามการตรวจใบรับรองได้ตามเงื่อนไข
Who should read
ผู้ใช้แพ็กเกจ nginx บน Ubuntu ตาม USN-9159-1 รวมถึงผู้ดูแล shared hosting ที่ต้องแยกแพ็กเกจ Ubuntu ออกจาก binary ของแผงควบคุม
Fix in short
อัปเดตแพ็กเกจให้ถึงรุ่นที่ประกาศ ตรวจ config แล้วรีสตาร์ตบริการให้ใช้ binary ใหม่ พร้อมทดสอบเว็บและการตรวจใบรับรองซ้ำ
Jump to steps

I noticed Ubuntu issued USN-9159-1 on 19 Nov 2026, covering vulnerabilities in several parts of nginx in a single advisory, so I broke down how each one affects web, mail proxy, or stream services. The code execution risk depends on the conditions for each CVE, while the client certificate verification bypass does not affect every HTTPS site. Check the config and installation source before prioritizing patches.

8 CVECovered by USN-9159-1
8.1CVSS 3.1 for CVE-2026-123007
4.8CVSS 3.1 for CVE-2026-120967
19 Nov 2026Ubuntu advisory date

What happened, by component in use

The memory bugs include writes beyond allocated memory and access to memory that has already been freed, or use-after-free. These bugs may crash workers or allow remote code execution. This table summarizes the conditions listed on Ubuntu's CVE pages.

CVE Conditions or components to check Stated impact
CVE-2026-123007 Incorrect HTTP/2 flow-control window handling Heap buffer overflow, worker crash, and possible code execution
CVE-2026-123633 HTTP/2 forwarding to a backend when few worker_connections slots remain Use-after-free and possible code execution
CVE-2026-121810 HTTP/3 enabled, with additional conditions outside the attacker's control Use-after-free, worker restart, and possible code execution
CVE-2026-113425 nginx acting as a mail proxy Use-after-free and possible code execution
CVE-2026-123634 Proxy destination name contains variables, and SSI or mirror sends a subrequest that resolves the same name Use-after-free in the resolver and possible code execution
CVE-2026-118899 ssl listen in http with TLS 1.3 enabled Loop while reading the request body, leaving the worker unable to serve requests
CVE-2026-120967 ssl_verify_client on in a non-default stream virtual server Client certificate verification bypass
CVE-2026-123640 ngx_stream_ssl_preread_module in use ClientHello causes incorrect values to be used for backend selection, potentially exposing data that should be blocked

The CVE pages for the HTTP/2, HTTP/3, mail proxy, and resolver vulnerabilities state that code execution requires ASLR to be disabled or the attacker to bypass ASLR. Even with ASLR enabled, service disruption remains a risk, so patching is still necessary. For the resolver, also check the variables and subrequests described in the table.

Check running binaryPackage or custom buildUse the same sourceCheck Ubuntu's fixed versionStart new binaryTest service and certificatesA config reload alone does not change the executable
Identify where the service gets nginx before choosing how to patch it and start new processes.

Read severity alongside the conditions

Ubuntu assigns CVE-2026-123007 High priority and lists a CVSS 3.1 score of 8.1 High, with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. An attacker can reach it over the network without an account or any user interaction, but the attack complexity is high. nginx classifies it as major on its security advisories page. The two projects use different rating criteria, so their ratings should not be treated as directly interchangeable.

CVE-2026-120967 has a CVSS 3.1 score of 4.8 Medium, with the vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N. The score is lower, but if client certificates are used to authorize access to a service, this bug may let an attacker bypass that check.

None of the 8 CVEs appear in the 18 Nov 2026 edition of KEV (catalogVersion: 2026.11.18). I checked the KEV JSON in CISA's official repository, so this edition has no KEV addition dates or remediation deadlines for these entries. Absence from KEV does not mean there is no exploitation in the wild.

Which packages each Ubuntu release needs

This table lists the package versions that USN-9159-1 specifies for the update, but that does not mean they fix all 8 CVEs on every Ubuntu release. Compare package versions within the same Ubuntu release, including the ubuntu and esm suffixes. Do not judge by the nginx version at the start of the package version alone, because Ubuntu can backport patches to an existing version.

Ubuntu nginx package version specified by the USN Channel
26.10 1.30.4-7ubuntu1.2 Ubuntu archive
26.04 LTS 1.28.3-2ubuntu1.13 Ubuntu archive
24.04 LTS 1.24.0-2ubuntu7.20 Ubuntu archive
22.04 LTS 1.18.0-6ubuntu14.23 Ubuntu 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 Ubuntu Pro with Legacy Support
14.04 LTS 1.4.6-1ubuntu3.9+esm10 Ubuntu Pro with Legacy Support

Each CVE affects a different set of Ubuntu releases. According to the USN, the two HTTP/2 vulnerabilities affect the releases listed in the table from 16.04 through 26.10, while HTTP/3 and the client certificate verification bypass affect only 26.04 and 26.10. This scope applies to Ubuntu packages. If you installed nginx yourself, check it separately.

Official sources still disagree

The USN lists CVE-2026-118899 as affecting only 24.04, 26.04, and 26.10, but its CVE page still lists 18.04, 20.04, and 22.04 as Vulnerable. For CVE-2026-123640, the USN lists only 26.04 and 26.10, but its CVE page still lists 18.04, 20.04, 22.04, and 24.04 as Vulnerable. Both CVE pages list Fixed for the releases covered by the USN, while CVE-2026-113425 and CVE-2026-123633 now show Fixed in line with the USN. Update according to the table, but for releases still marked Vulnerable, do not assume these packages fix those two CVEs yet. Check the changelog and continue tracking each CVE's status.

Check the installation source before patching

On shared hosting, check which binary the service actually runs. The nginx on PATH may differ from the one the service calls. If you use DirectAdmin or a separate build system, check that system's procedure too. Even after updating Ubuntu packages, you still need to check whether the other binary has been patched.

cat /etc/os-release
command -v nginx
sudo systemctl show nginx -p ExecStart
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'nginx*' 'libnginx-mod-*'
apt-cache policy nginx

If ExecStart calls a different binary from the one on PATH, adjust the following commands to use the binary and config options from the existing unit. According to the command-line documentation, -V shows build options, while -T displays the config, including included files.

nginx -V 2>&1
sudo nginx -T 2>&1 | grep -nE 'http2|http3|quic|ssl_verify_client|ssl_preread|resolver|proxy_pass|mirror|ssi|worker_connections|mail[[:space:]]*\{'

Use the search results to find the parts of the config that need further reading. Also check whether each directive is in http or stream, and which server contains it. Do not disable certificate verification to avoid the triggering conditions, because that would remove the protection it provides.

Update, then have the service use the new binary

  1. Plan a maintenance window Back up the config and assess the impact on websites and existing connections.
  2. Confirm the package source Check Installed, Candidate, and Pro/ESM entitlements for the Ubuntu release in use.
  3. Install patches Update nginx packages and installed modules from the same source.
  4. Test and restart Check that the config passes, start new processes, and test the services, including client certificates.

Once you have confirmed that you use Ubuntu packages, update with APT. Read the list of changes before accepting, and check that nginx and its modules are not held, causing patches to be skipped.

sudo apt update
apt-cache policy nginx
sudo apt upgrade
sudo nginx -t && sudo systemctl restart nginx
systemctl is-active nginx

For releases that require Ubuntu Pro, check pro status to confirm the entitlement and that the relevant ESM services are enabled, following the ESM documentation. If you do not yet see the Candidate listed in the table, do not immediately conclude that no patch is available. It may be a repository or entitlement issue. For packages from other sources, follow the advisories from their package maintainers.

A restart may drop connections, so schedule it appropriately. According to the Controlling nginx documentation, reloading the config does not start the master with a new executable. This example therefore restarts after the config passes, then retests the websites, backends, and certificate verification.

Check for signs of exploitation and decide how urgently to act

The referenced advisories do not provide IOCs or request signatures. If you find worker crashes, segmentation faults, or sustained CPU usage, investigate further, but these symptoms alone cannot identify a particular CVE or establish that an intrusion has occurred. Start with the journal, then read the logs at the configured error_log location.

sudo journalctl -u nginx --since '2026-11-18' --no-pager
sudo journalctl -k --since '2026-11-18' --no-pager | grep -iE 'nginx|segfault'
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'nginx*' 'libnginx-mod-*'

Expand the date range to match your log retention and preserve evidence when you find unusual behavior. Even without a crash, certificate verification may still have been bypassed or the wrong destination selected.

Verify the results after updating

Check the package version and processes after the restart, then test the websites and services in use. If you use client certificates to authorize access to a service, also test that unauthorized connections are still rejected. Being able to open a web page alone does not establish that certificate verification works correctly.

I recommend prioritizing patches for services that accept external connections and meet the conditions in the table, especially HTTP/2, HTTP/3, mail proxy, and stream services that verify client certificates. Prepare the tests you will run after restarting in advance, without waiting for an outage. If you have read the article on nginx and config checks, review this set of CVEs separately too. Fixing a different set of bugs does not confirm that these have been addressed.

Sources: Ubuntu USN-9159-1, individual Ubuntu CVE pages linked in the table, nginx security advisories, CISA KEV JSON, nginx command-line, nginx control, Ubuntu package management, Ubuntu Pro ESM Information current as of 19 Nov 2026. I'll come back and update it later.

Want us to set this up?

Get help with server setup, configuration, migration, or troubleshooting. Save time for the work that matters.

Get a quote

Hit something like this? Stuck somewhere?

Come trade notes on the LinuxThai board

→ Continue on the board

Comments 0

No comments yet — be the first