Ubuntu nginx CVE-2026-118899 TLS DoS Patches for Older LTS
Anyone running nginx on Ubuntu 18.04, 20.04 or 22.04 with TLS 1.3 enabled should plan to update soon, check ESM entitlement if using packages from that channel, then restart the service to use the new binary.
1-minute summary
- Symptom / problem
- การเชื่อมต่อ TLS 1.3 ที่สร้างเป็นพิเศษทำให้ nginx worker วนลูปจนหยุดให้บริการ อีกสองบั๊กเกี่ยวกับ ClientHello และการใช้ try_files ร่วมกับ alias ต้องตรวจ config แยกกัน
- Who should read
- ผู้ใช้แพ็กเกจ nginx ของ Ubuntu ตาม USN-9182-1 โดยเงื่อนไขและขอบเขตรุ่นต่างกันในแต่ละ CVE
- Fix in short
- อัปเดต nginx และโมดูลให้ถึง revision ของ Ubuntu รุ่นที่ใช้ ตรวจ config แล้วรีสตาร์ตและทดสอบบริการ ถ้าใช้แพ็กเกจ ESM ต้องมีสิทธิ์ Ubuntu Pro ที่ครอบคลุม
I noticed Ubuntu released USN-9182-1 on 20 Nov. 2026 with another set of nginx patches, so I put together the points that administrators of older LTS releases need to check. Anyone who already updated under USN-9159-1 should compare the revision again. That notice did not yet fix TLS DoS and ClientHello on some Ubuntu releases.
What happened, and how this differs from the previous notice
The main issue is CVE-2026-118899, which affects configurations using listen with ssl in the http block and TLS 1.3 enabled. An attacker does not need to log in; sending a specially crafted TLS connection is enough to make a worker loop while reading an HTTP request body. That worker stops accepting new connections and stops processing existing connections. The result is denial of service, or DoS.
The other two issues require separate configuration checks.
| CVE | What to check | Impact according to official sources |
|---|---|---|
| CVE-2026-123640 | ngx_stream_ssl_preread_module reading ClientHello |
Spoofing variable values used to select a virtual server, allowing forwarding to a backend that should be blocked and potentially exposing sensitive information |
| CVE-2026-125283 | try_files and alias using variables from map with certain regex capture patterns |
A worker encounters a segmentation fault and stops running |
Compared with USN-9159-1 dated 19 Nov. 2026, this set adds patches for several older releases.
- CVE-2026-118899 was previously fixed in 24.04/26.04/26.10; this set adds fixes for 18.04/20.04/22.04
- CVE-2026-123640 was previously fixed in 26.04/26.10; this set adds fixes for 18.04/20.04/22.04/24.04
- CVE-2026-125283 is added in this notice
For CVE-2026-123007 and the previous set of bugs, see the nginx roundup for USN-9159-1.
Severity and evidence of exploitation
Ubuntu's page for CVE-2026-118899 assigns CVSS v4.0 = 8.7 High with vector CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N and CVSS v3.1 = 7.5 High with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. This means it can be attacked over the network without an account or waiting for anyone to click anything. The main impact is an unresponsive service.
The other two both have a CVSS v3.1 score of 5.3 Medium, but their impacts differ.
| CVE | CVSS v3.1 vector |
|---|---|
| CVE-2026-123640 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| CVE-2026-125283 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L |
Ubuntu assigns all three a Medium priority, while nginx rates TLS DoS as major and the other two as minor. Each project has its own rating criteria, so these severity labels cannot be compared directly with CVSS scores.
None of the three CVEs appears in KEV version 2026.11.18, based on a check of CISA's KEV JSON, so this version has no date added or remediation deadline for any of them. The cited Ubuntu notices and nginx security page do not state that any of the three has been exploited in the wild, and do not identify RCE as an impact. Absence from KEV does not mean no one is exploiting them.
Fixed package versions must be checked against Ubuntu
Use the revision from USN-9182-1 shown in the table, or a newer version within the same Ubuntu release.
| Ubuntu | Revision listed in USN-9182-1 | Patch channel |
|---|---|---|
| 26.10 | 1.30.4-7ubuntu1.3 |
Ubuntu archive |
| 26.04 LTS | 1.28.3-2ubuntu1.14 |
Ubuntu archive |
| 24.04 LTS | 1.24.0-2ubuntu7.21 |
Ubuntu archive |
| 22.04 LTS | 1.18.0-6ubuntu14.24 |
Ubuntu archive |
| 20.04 LTS | 1.18.0-0ubuntu1.7+esm6 |
Ubuntu Pro / ESM |
| 18.04 LTS | 1.14.0-0ubuntu1.11+esm7 |
Ubuntu Pro / ESM |
| 16.04 LTS | 1.10.3-0ubuntu0.16.04.5+esm12 |
Ubuntu Pro with Legacy Support |
| 14.04 LTS | 1.4.6-1ubuntu3.9+esm11 |
Ubuntu Pro with Legacy Support |
The CVE pages state that 14.04/16.04 are not affected by TLS DoS and ClientHello, so a row in the table does not mean that release is affected by all three issues. There are also separate patches for libnginx-mod-stream in 18.04/20.04/22.04/24.04. If this module is installed, update it too.
Checked on 20 Nov. 2026, the CVE-2026-118899 page still shows 18.04/20.04/22.04 as Vulnerable, CVE-2026-123640 still shows 18.04/20.04/22.04/24.04 as Vulnerable, and CVE-2026-125283 still shows all eight releases in the table as Vulnerable, but USN-9182-1 announces the fixed revisions listed here. Compare the revision from the USN with the installed package, then continue monitoring the individual CVE statuses.
Upstream states that all three are fixed in nginx 1.30.7+ or 1.31.9+, while Ubuntu can backport the patches to existing versions.
There is also a difference in the affected version ranges. Upstream states that ClientHello affects versions starting from 1.15.2, but the Ubuntu team also found the problematic SNI/ALPN code in 18.04's 1.14.0. That means the Ubuntu package revision must also be checked. Looking only at the version from nginx -v is not enough.
Check the installation source and configuration before updating
Start by checking the system version, packages and binary invoked by the service. Anyone using DirectAdmin or a custom build should check whether the binary found in PATH matches the one serving traffic. The APT commands below apply only to Ubuntu packages.
cat /etc/os-release
command -v nginx
systemctl show nginx -p ExecStart
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'nginx*' 'libnginx-mod-*'
apt-cache policy nginx libnginx-mod-stream
apt-mark showhold
According to the nginx documentation, -V shows build options, while -T tests and displays the configuration. Use the same binary and configuration as the service. Matching lines are only a starting point; read the http/stream blocks and related variables too.
nginx -V 2>&1
sudo nginx -T 2>&1 | grep -nE 'listen.*ssl|ssl_protocols|ssl_preread|try_files|alias|map[[:space:]]'
If using ESM packages, check pro status to confirm entitlement and that the required services are enabled. If Candidate is still below the version in the table, do not assume the update is complete; check repositories, package holds and Pro entitlement. Instructions for checking and enabling esm-infra/esm-apps are in the Ubuntu Pro documentation.
Update, then start the service with the new binary
- Prepare a maintenance window Back up the configuration and plan for connections that may drop
- Check package sources Compare Installed with Candidate and check Pro/ESM entitlement for the Ubuntu release
- Install all patches Update nginx along with installed modules from the same source
- Check and restart Make sure the configuration passes before starting new processes, then check the service and revision again
Use Ubuntu's APT and read the package list before accepting, because apt upgrade updates other packages too. If nginx or its modules are kept back, resolve that condition before considering the work complete.
sudo apt update
apt-cache policy nginx libnginx-mod-stream
sudo apt upgrade
sudo nginx -t && sudo systemctl restart nginx
systemctl is-active nginx
dpkg-query -W -f='${binary:Package}\t${Version}\n' 'nginx*' 'libnginx-mod-*'
Restarting may drop connections. According to the nginx control documentation, reloading the configuration keeps the existing master, and old workers wait for pending work to finish. Make sure the service is using the new binary. Then test the website, uploads and stream backend selection.
This USN does not specify a workaround, so focus on updating packages. If the binary comes from another source, track patches from that provider separately from APT.
Check for signs of exploitation and decide how urgently to update
The cited Ubuntu notices and nginx security page provide no IOC or request signature to confirm exploitation. Check worker CPU usage, increased timeouts, and worker crashes or segmentation faults, then correlate the timing with the journal and error_log.
ps -C nginx -o pid,ppid,pcpu,etime,args
sudo journalctl -u nginx --since '2026-11-18' --no-pager
sudo journalctl -k --since '2026-11-18' --no-pager | grep -iE 'nginx|segfault'
Adjust the date range to cover the logs you want to inspect. For ClientHello, check whether backend selection still follows the access rules. If you find abnormal behavior, collect logs and process information before restarting.
High CPU usage or worker crashes can have other causes. Finding no symptoms does not confirm that the system is safe either. To check whether all patches are installed, inspect the installed revision and confirm that the processes are using the new binary.
I think older LTS machines with TLS 1.3 enabled and accepting external connections should be patched in the next available maintenance window, because an attacker can make a worker stop serving connections without an account. If the configuration meets the conditions for the stream bug or try_files with alias, install all the updates in the same window. Do not wait for symptoms before checking the revision.
Sources: Ubuntu USN-9182-1 (JSON), USN-9159-1, Ubuntu CVE-2026-118899, CVE-2026-123640, CVE-2026-125283, nginx security advisories, CVE Records from the CVE Program: CVE-2026-118899, CVE-2026-123640, CVE-2026-125283, CISA KEV JSON, nginx command-line, nginx control, Ubuntu package management, Ubuntu Pro ESM Information current as of 20 Nov. 2026. I will come back and update this later.
Want us to set this up?
Get help with server setup, configuration, migration, or troubleshooting. Save time for the work that matters.
Hit something like this? Stuck somewhere?
Come trade notes on the LinuxThai board



Comments 0
No comments yet — be the first