On this page (7 sections)
On 12 November 2026 Ubuntu published USN-9090-1, a security notice that bundles several Apache HTTP Server fixes. They range from crashes in individual modules to flaws Ubuntu says could possibly allow arbitrary code execution, including one in mod_http2 that the Apache project rates critical.
If you run Apache from Ubuntu packages, whether on a VPS, a dedicated server or a shared hosting node you administer, this update is worth applying promptly. The notice says a standard system update makes all the necessary changes.
What the notice covers
USN-9090-1 lists five issues. The descriptions below follow Ubuntu's notice and the Apache 2.4 vulnerabilities page, with Apache's own severity ratings where it gives them.
| CVE | Module | Impact per sources | Apache rating |
|---|---|---|---|
| CVE-2026-119618 | mod_http2 | Heap corruption; crash or possibly arbitrary code execution (Ubuntu) | Critical |
| CVE-2026-106023 | mod_md | NULL pointer dereference; child process crash | Important |
| CVE-2026-109163 | mod_vhost_alias | One-byte stack buffer overflow; crash or possibly code execution (Ubuntu) | Low |
| CVE-2026-42528 | mod_dav | Crash of child processes by someone allowed to create WebDAV locks | Moderate (CVSS 4.3 in GitHub advisory) |
| CVE-2026-42356 | CGI internal redirects | Redirect target could be treated as a CGI program; possible code execution (Ubuntu) | Not shown in the sources |
Technical details in plain terms
These are memory-safety and logic bugs, the kind that appear in long-lived C code. Two of them are crashes (a NULL pointer dereference in mod_md and a memory size miscalculation in mod_dav). Two are buffer or heap corruption (mod_http2 and mod_vhost_alias), where Ubuntu says arbitrary code execution is possible in addition to a crash.
The mod_http2 flaw, CVE-2026-119618, is described by Apache as a concurrency problem in assign_headers() that can lead to remote code execution. Apache lists it as affecting 2.4.55 through 2.4.70, and credits Anthropic's OSS Scanner and researchers at Google Cloud Vulnerability Research. Ubuntu describes the trigger as certain request headers, from a remote attacker.
The mod_dav issue needs an attacker who already has permission to create WebDAV locks, so it matters mainly where WebDAV is enabled for users you do not fully trust. The mod_md issue is triggered during HTTP request processing and affects a wide range of releases, from 2.4.30 through 2.4.70 according to Apache.
Where the sources differ
Version ranges are not identical across sources. The CVE record for CVE-2026-109163 says it affects 2.4.69, while Apache lists 2.4.69 and 2.4.70. The GitHub advisory for CVE-2026-106023 says through 2.4.69, while Apache lists through 2.4.70. Ubuntu also says the mod_vhost_alias flaw could possibly allow code execution, while Apache's rating is low. Treat the vendor package fix as the reference, and do not rely on the upstream version number alone, because distributions backport fixes.
Who is affected
Ubuntu lists fixed apache2 packages for releases from 14.04 LTS through 26.10. Not every issue applies everywhere:
- CVE-2026-106023 (mod_md) and CVE-2026-119618 (mod_http2) only affected Ubuntu 20.04 LTS, 22.04 LTS, 24.04 LTS, 26.04 LTS and 26.10.
- CVE-2026-42356 (CGI internal redirects) only affected Ubuntu 26.04 LTS and 26.10.
- Whether you are exposed also depends on which modules you have enabled. A server that does not load mod_http2, mod_md, mod_dav or mod_vhost_alias is not exposed to that module's bug.
Servers built from upstream source rather than Ubuntu packages should move to Apache 2.4.71, which Apache says fixes the mod_http2, mod_md and mod_vhost_alias issues. The mod_dav issue was fixed in 2.4.69.
How to check your exposure
First see which Apache package version is installed. Compare the output with the fixed versions in the table below.
apt-cache policy apache2Next, list the Apache modules currently loaded. Look for http2, md, dav and vhost_alias in the output.
apache2ctl -M| Ubuntu release | Fixed apache2 version |
|---|---|
| 26.10 | 2.4.68-1ubuntu6.2 |
| 26.04 LTS | 2.4.66-2ubuntu2.8 |
| 24.04 LTS | 2.4.58-1ubuntu8.19 |
| 22.04 LTS | 2.4.52-1ubuntu4.27 |
| 20.04 LTS (Ubuntu Pro) | 2.4.41-4ubuntu3.23+esm11 |
| 18.04 LTS (Ubuntu Pro) | 2.4.29-1ubuntu4.27+esm15 |
| 16.04 LTS (Ubuntu Pro, Legacy Support) | 2.4.18-2ubuntu3.17+esm24 |
| 14.04 LTS (Ubuntu Pro, Legacy Support) | 2.4.7-1ubuntu4.22+esm19 |
What to do now
- Run apt-cache policy apache2 and compare the installed version with the table above.
- Run apache2ctl -M and note whether mod_http2, mod_md, mod_dav or mod_vhost_alias are loaded.
- Update the apache2 packages with the commands below.
- Confirm the new version and that Apache is running.
- Disable modules you do not need, and restrict WebDAV lock permissions if you use mod_dav.
- On Ubuntu 20.04 LTS and older, enable Ubuntu Pro to receive the fix, or plan an upgrade to a supported release.
- Check your error log for unexpected child process crashes around and before the update.
Refresh package lists and upgrade only the Apache packages. This installs the fixed version from Ubuntu's archive.
sudo apt update && sudo apt install --only-upgrade apache2 apache2-binValidate the configuration, then confirm the service is active after the update.
sudo apache2ctl configtest && systemctl status apache2Detection and monitoring afterwards
Several of these bugs end in a crashed child process. Apache normally respawns children, so crashes can go unnoticed. Search the error log for segmentation faults or child exit signals, which would show repeated crashes.
sudo grep -i 'segfault\|exit signal' /var/log/apache2/error.logThe sources do not report any exploitation in the wild, so a clean log is expected, but a pattern of crashes before patching is worth investigating. After updating, keep an eye on uptime and certificate status; Webforta Monitor can alert on outages and certificate changes, and the free SSL checker gives a quick look at what your server presents. For background, see What is a WAF? on how filtering in front of a server can reduce exposure, though it is no substitute for patching.
Timeline
- 2026-04-27: CVE-2026-42528 report received by the Apache security team.
- 2026-10-01: Apache 2.4.69 released with the mod_dav fix.
- 2026-10-26 and 2026-11-03: CVE-2026-119618 reported to the Apache security team by Anthropic and Google respectively.
- 2026-11-11: Apache 2.4.71 released with fixes for CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163.
- 2026-11-12: Ubuntu publishes USN-9090-1.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
