How To

Patch Apache CVE-2026-119618 on Ubuntu 26.04 / 24.04 / 22.04

On November 11, 2026, Apache httpd 2.4.71 shipped the fix for CVE-2026-119618, a critical race in mod_http2. The bug sits in header handling, corrupts heap memory and can end in remote code execution. Red Hat scores it CVSS 9.8 and states that public research has shown a reliable exploit against a default configured server with mod_http2 enabled. The current apache2 builds for Ubuntu 26.04, 24.04 and 22.04 all carry affected code, the 22.04 one included, and there is no CVE-2026-119618 Ubuntu package to install yet.

Original content from computingforgeeks.com - post 189502

Ubuntu has not published a USN or fixed packages yet. This guide covers what you can do on Ubuntu 26.04, 24.04 and 22.04 right now. You can check whether a server is exposed, shut HTTP/2 off in a way that actually holds, or patch from the ondrej/apache2 PPA where a build exists. Every step was run in November 2026 on fresh Ubuntu cloud images with default security settings, and each control is proved with curl rather than assumed.

Ubuntu’s patch status for CVE-2026-119618

The Apache advisory lists httpd 2.4.55 through 2.4.70 as affected, plus the standalone mod_h2 module from 2.0.8 through 2.0.42. On November 12, 2026 the ubuntu.com CVE page still returned 404, the USN list had no apache2 notice, and the Ubuntu CVE tracker entry marked every release as needs-triage with priority high. That is the state this table records.

ReleaseArchive apache2 buildmod_http2 insidehttp2 on by defaultUSN fixPPA 2.4.71 build
Ubuntu 26.04 (resolute)2.4.66-2ubuntu2.72.0.42NoNone yetNo
Ubuntu 24.04 (noble)2.4.58-1ubuntu8.182.0.42 backportNoNone yetYes
Ubuntu 22.04 (jammy)2.4.52-1ubuntu4.262.0.42 backportNoNone yetYes

Two columns decide your risk, and they point in opposite directions. The module isn’t loaded after a plain apt install apache2 on any of the three releases, so a stock install is not exposed. The moment someone runs a2enmod http2, a common step when setting up TLS, the server answers HTTP/2 and sits in the range Red Hat says has a working exploit. So for each host, what matters is its history: whether anyone, or any automation, ever turned HTTP/2 on. Answer that with the checks below, not from memory. Debian is ahead here: trixie already has 2.4.71 through DSA-6620-1, so Debian 13 hosts built from our Debian LAMP stack guide can patch with a plain upgrade.

The mod_http2 backport that puts 22.04 in scope

Ubuntu 22.04 ships httpd 2.4.52, which is below the affected upstream range, and that’s an easy reason to skip it. Don’t. Ubuntu’s security team replaced the bundled HTTP/2 module with a newer upstream copy when it fixed CVE-2026-48913, and the Ubuntu tracker note for this CVE says the same about the stable releases. The module version, not the httpd version, is what matters here.

The changelog on our 22.04 lab server names the backport, and the shared object carries the version string to match:

zgrep -n -B3 -A4 "update to version 2.0.42" /usr/share/doc/apache2/changelog.Debian.gz
grep -a -c "2\.0\.42" /usr/lib/apache2/modules/mod_http2.so
a2query -M

Line 131 says CVE-2026-48913.patch: update to version 2.0.42 of the http2 module, and 2.0.42 is the last mod_h2 release inside the affected range. The MPM is event, which matters on 22.04 because its http2.conf wraps the Protocols h2 h2c http/1.1 line in <IfModule !mpm_prefork>. On the default MPM that line applies.

Ubuntu 22.04 apache2 changelog showing the mod_http2 2.0.42 backport inside the CVE-2026-119618 range

Reading the config files rather than probing, a 22.04 server on prefork (common wherever mod_php is still in use) skips that Protocols line, so the shipped file alone does not turn h2 on there. We did not test prefork in the lab, so do not lean on it: run the curl probes below on every 22.04 host. Treat 24.04 and 26.04 as exposed whatever the MPM, because their http2.conf has no such guard and the Apache HTTP/2 guide says prefork supports HTTP/2 with restrictions.

Version and module checks on your server

Start with what the box actually runs. These three commands tell you the build, whether Ubuntu has shipped a fix for it, and whether mod_http2 is loaded. Run them on every Apache host, including the internal ones, since a reverse proxy behind a load balancer is still reachable by whatever talks to it.

apt-cache policy apache2
apt changelog apache2 2>/dev/null | grep -c CVE-2026-119618
a2query -m http2

Each answer maps to a decision:

  • A changelog count of 0 means the installed Ubuntu build doesn’t carry the fix.
  • No module matches http2 means the module is off and the host is not reachable through this bug today.
  • http2 (enabled by site administrator) means the host needs a workaround or a patched build now.

On Ubuntu 26.04 the latest changelog entry for the newest archive build, 2.4.66-2ubuntu2.7, fixes CVE-2026-46729, a denial of service, and the count for this CVE reads 0 there today:

Ubuntu 26.04 apache2 2.4.66-2ubuntu2.7 version check with no CVE-2026-119618 entry in apt changelog

The changelog check has a blind spot: apt changelog reads from changelogs.ubuntu.com and showed no entry for the PPA build in our run. For those, read the local copy with zgrep on /usr/share/doc/apache2/changelog.Debian.gz, as the PPA section below does. The apt and apt-get cheat sheet covers the policy and changelog commands in more depth.

HTTP/2 exposure, confirmed with curl

A loaded module only tells half the story. What an attacker cares about is whether the listener negotiates HTTP/2, and Apache offers it three ways: h2 over TLS, an h2c upgrade on plain HTTP, and h2c with prior knowledge. Probe all three from the server itself:

curl -sk --http2 -o /dev/null -w "%{http_version}\n" https://localhost/
curl -s --http2 -o /dev/null -w "%{http_version}\n" http://localhost/
curl -s --http2-prior-knowledge -o /dev/null -w "%{http_version}\n" http://localhost/

Our 24.04 lab host had a2enmod ssl http2 and the default SSL site enabled, which is what a typical HTTPS setup on Ubuntu looks like. All three probes came back 2, so both port 443 and plain port 80 spoke HTTP/2. The only Protocols line on the box was the one shipped in mods-available/http2.conf.

curl probes on Ubuntu 24.04 returning HTTP/2 over TLS, h2c upgrade and prior knowledge with mod_http2 enabled

Read the results against two conditions:

  • Any probe that prints 2 marks the host as exposed until it runs a patched build.
  • The first two probes print 1.1 and the third prints 0 (no HTTP response at all) when HTTP/2 is off on that listener.

Repeat the probes against each virtual host name you serve, because a vhost can carry its own Protocols line and answer differently from localhost. Probe from outside as well if a load balancer or CDN terminates TLS in front of Apache. In that layout the edge may speak HTTP/2 to clients while Apache only sees HTTP/1.1, or the reverse, and only the hop that reaches Apache with HTTP/2 matters for this bug. Closing port 80 with UFW firewall rules stops outside h2c probes but leaves h2 over TLS on 443 untouched, so a firewall is no substitute for the controls below.

Disabling mod_http2 with a2dismod

Until a fixed package lands, the safest control is to unload the vulnerable code. Red Hat notes that servers serving only HTTP/1.1 are not affected, and disabling the module guarantees that no listener or vhost can bring HTTP/2 back by accident. The cost is HTTP/2 itself: browsers fall back to HTTP/1.1 over TLS, which works fine.

sudo a2dismod http2
sudo apache2ctl configtest
sudo systemctl restart apache2

Restart, as the a2dismod output asks, then probe again. On Ubuntu 26.04 the three probes then returned 1.1, 1.1 and 0, and a2query -m http2 reported the module as disabled by the site administrator:

a2dismod http2 on Ubuntu 26.04 with curl probes falling back to HTTP/1.1

Configuration management can undo this without anyone noticing. If Ansible, Puppet or a cloud-init template runs a2enmod http2, change it there as well, or the next run quietly reopens the hole and the module is back after the following restart. Add the three curl probes to whatever monitors the host so a regression shows up as a failed check rather than a surprise. When the patched package arrives, re-enable the module in the same change that installs it, so HTTP/2 never comes back on vulnerable code.

A Protocols line that has to sit in each vhost

Some sites cannot unload the module, usually because another vhost or a proxy rule depends on it. The usual advice is a server-wide Protocols http/1.1, and on Ubuntu we found that it didn’t hold. We dropped it into conf-available, enabled it with a2enconf, restarted Apache and probed again. TLS and prior knowledge both still answered 2.

What did work was a Protocols http/1.1 line inside each <VirtualHost> block. This sed inserts it before the closing tag of both default sites; repeat it for every site file you have added:

sudo sed -i '/<\/VirtualHost>/i \\tProtocols http/1.1' /etc/apache2/sites-available/000-default.conf /etc/apache2/sites-available/default-ssl.conf
sudo grep -rn "^\s*Protocols" /etc/apache2/
sudo apache2ctl configtest
sudo systemctl restart apache2

With http2 still enabled, the probes now returned 1.1, 1.1 and 0. The grep output explains the earlier failure. The module’s own http2.conf still sets Protocols h2 h2c http/1.1, and in the httpd source a second Protocols line in the same server context appends to that list instead of replacing it. A vhost with its own non-empty list uses that list, which is why only the per-vhost line held. This is how httpd behaves, not a quirk of one run.

Apache Protocols http/1.1 test on Ubuntu: server-wide conf still answers HTTP/2, per-vhost line drops to HTTP/1.1

This control is weaker than a2dismod for one reason: every new site needs the line, and one forgotten vhost puts the whole process back in reach. Use it only where the module must stay loaded, and probe each server name after every site change. The LAMP stack guide for Ubuntu 26.04 shows where those site files live.

The ondrej/apache2 PPA on 24.04 and 22.04

The ondrej/apache2 PPA, run by Ondřej Surý, one of the Debian apache2 maintainers, published 2.4.71 builds for Noble and Jammy on November 11, 2026. It is a third-party repository, not the Ubuntu security archive, so weigh that before adding it to production. It is still the only way to run the fixed upstream code on Ubuntu today without building from source.

sudo add-apt-repository -y ppa:ondrej/apache2
apt-cache policy apache2
sudo apt-get install -y --only-upgrade apache2

The upgrade touched these packages on our two lab hosts:

  • On 24.04, apache2, apache2-bin, apache2-data and apache2-utils moved to 2.4.71 with nothing new installed.
  • On 22.04, the same four packages moved and liblua5.4-0 was installed as a new dependency.

Restart Apache, then confirm the changelog shipped in the package names the CVE, since apt changelog stays silent for PPA builds:

sudo systemctl restart apache2
apache2 -v
zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz

We got Apache/2.4.71 (Ubuntu) and a count of 1. HTTP/2 still answered 2 afterwards, which is the point of patching: the protocol stays on and the vulnerable code is gone.

Ubuntu 24.04 apache2 upgraded to 2.4.71 from the ondrej/apache2 PPA with the CVE-2026-119618 changelog entry

Do not trust the version string inside the module as proof. The mod_http2.so in the PPA build still contains the text 2.0.42, the same as the vulnerable Ubuntu build, so a scanner that greps the binary will flag a patched host. The changelog entry is the evidence that counts.

The 22.04 changelog shows the entry in full, with the two other CVEs that 2.4.71 closes (CVE-2026-106023 in mod_md and CVE-2026-109163 in mod_vhost_alias):

Ubuntu 22.04 PPA apache2 2.4.71 changelog naming CVE-2026-119618, CVE-2026-106023 and CVE-2026-109163

One more consequence of the PPA: unattended-upgrades will not touch it. Its Allowed origins on both releases cover only the Ubuntu and ESM pockets, and a dry run applied pin -32768 to the PPA package lists. Future PPA fixes need a manual upgrade or an extra origin in the unattended-upgrades configuration, so put the host on a patch rota.

No PPA build for Ubuntu 26.04

The PPA has builds for Noble and Jammy only. Adding it on Ubuntu 26.04 succeeds, then breaks the next update:

apt update error on Ubuntu 26.04: the ondrej/apache2 PPA has no resolute Release file

If you added it already, delete the source file so apt stops failing, then fall back to a2dismod http2 until Ubuntu ships a fixed resolute build:

sudo rm /etc/apt/sources.list.d/ondrej-ubuntu-apache2-resolute.sources
sudo apt-get update

Leaving the broken entry in place means every apt-get update ends on that error. It buries real repository failures in the noise and trips any script that checks the exit status, which is a poor trade for a source that offers nothing on this release.

Rolling back to the Ubuntu archive build

Once Ubuntu publishes its USN, you’ll probably want to return to the archive packages so unattended-upgrades covers Apache again. ppa-purge removes the PPA and downgrades every package that came from it in one step. If the archive build you’re going back to still lacks the fix, run sudo a2dismod http2 first:

sudo apt-get install -y ppa-purge
sudo ppa-purge -y ppa:ondrej/apache2
systemctl is-active apache2

We ran it on both releases. On 22.04 it downgraded four packages to 2.4.52-1ubuntu4.26 and on 24.04 to 2.4.58-1ubuntu8.18, printed PPA purged successfully each time, and Apache stayed active. On 24.04 the PPA’s deb822 .sources file stays on disk with Enabled: no, so apt ignores it. Today the purge is a downgrade back into the affected build. Only run it once the USN lands and the version table in apt-cache policy apache2 lists an Ubuntu archive build above 2.4.52-1ubuntu4.26 or 2.4.58-1ubuntu8.18; the Candidate line keeps showing the PPA build while the PPA is enabled.

ppa-purge on Ubuntu 22.04 downgrading apache2 back to 2.4.52-1ubuntu4.26 from the Ubuntu archive

Before and after the rollback, run the curl probes again. A PPA-patched host normally has http2 enabled, so if the archive build still lacks the fix, run sudo a2dismod http2 before purging and keep it off until apt changelog apache2 names CVE-2026-119618 (any count above zero). A rollback done too early silently trades a patched host for an exposed one.

Audit checklist for every Apache host

Work through each server against these conditions. Each one is a statement that must be true, and the commands above prove it:

  1. The apache2 changelog on the host names CVE-2026-119618, or mod_http2 is disabled.
  2. All three curl probes return 1.1, 1.1 and 0 on every server name, unless the patched build is installed.
  3. Ubuntu 22.04 hosts were checked like the others, regardless of the 2.4.52 version number.
  4. Any Protocols http/1.1 workaround sits inside each VirtualHost block, not only in a conf file.
  5. Configuration management no longer re-enables http2 on unpatched hosts.
  6. Ubuntu 26.04 hosts carry no ondrej/apache2 source that breaks apt update.
  7. PPA-patched hosts are on a manual patch rota, since unattended-upgrades ignores the PPA.

Recheck the Ubuntu CVE tracker and the USN list daily until apache2 updates appear, then patch from the archive and drop the workaround. Ubuntu servers run by a control panel such as DirectAdmin are the exception, because the panel installs and builds its own Apache, so follow the DirectAdmin CustomBuild Apache patch on those hosts instead. The Apache httpd 2.4 vulnerability list and the Red Hat CVE page carry the vendor details. Our nginx CVE-2026-15176 walkthrough uses the same check and patch pattern for the other common web server.

Keep reading

Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) Ubuntu Upgrade Ubuntu 24.04 to Ubuntu 26.04 LTS (Step by Step) UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 Security UFW Firewall Commands with Examples on Ubuntu 26.04 / 24.04 PHP2Shell (CVE-2026-109618, CVE-2026-109619): Check and Patch PHP Php PHP2Shell (CVE-2026-109618, CVE-2026-109619): Check and Patch PHP Git CVE-2026-111760: Check and Patch the Recursive Clone RCE Git Git CVE-2026-111760: Check and Patch the Recursive Clone RCE Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Cloud Deploy Collabora Online Office on Ubuntu with Let’s Encrypt SSL Install Caddy Web Server on Ubuntu 26.04 / 24.04 and Debian 13 Ubuntu Install Caddy Web Server on Ubuntu 26.04 / 24.04 and Debian 13

Leave a Comment

Press ESC to close