CVE-2026-119618: Is Your Apache on Ubuntu Affected? Check, Patch or Disable HTTP/2

CVE-2026-119618: Is your Apache on Ubuntu affected? Check, patch or disable HTTP/2

CVE-2026-119618 is a critical bug in Apache’s HTTP/2 module that can give an unauthenticated attacker code execution on your web server. On Ubuntu or Debian you’re affected if two things are true: the http2 module is enabled, and your apache2 package is older than the fixed version for your release. The Apache version number doesn’t tell you which. Ubuntu 22.04 ships Apache 2.4.52, which is “below” the upstream range, and it’s still affected.

I spun up throwaway Ubuntu 22.04, 24.04 and 26.04 containers, installed the original release packages, turned HTTP/2 on, patched them and turned HTTP/2 back off. Every command and output below comes from those runs. No real servers were harmed.

Table of Contents

Quick Start

Run these three on the server. You don’t need root for any of them.

Terminalbash
dpkg-query -W apache2
test -e /etc/apache2/mods-enabled/http2.load && echo "http2: enabled" || echo "http2: disabled"
zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz
  • http2 disabled: you’re not exposed to this bug. Patch anyway with your normal updates.
  • http2 enabled and the last command prints 0: you’re running an unpatched package. Patch now, or switch HTTP/2 off until you can.
  • The last command prints 1 or more: the fix is installed. Make sure Apache was restarted after the update (see the restart check).

The fix on Ubuntu is a normal update:

Terminalbash
sudo apt update
sudo apt install --only-upgrade apache2 apache2-bin apache2-data apache2-utils
sudo systemctl restart apache2

What CVE-2026-119618 is (and who found it)

It’s a race condition in assign_headers() inside mod_http2. Threads that share a resource without proper locking can corrupt the heap, and according to the Apache httpd security page that “can lead to RCE”. Apache rates it critical. Ubuntu rates it High with the reason “This is a remote RCE.”

Upstream, it affects Apache HTTP Server 2.4.55 through 2.4.70 and the standalone mod_h2 module 2.0.8 through 2.0.42. The fix is in Apache 2.4.71, released November 11, 2026, together with two smaller bugs (CVE-2026-106023 in mod_md and CVE-2026-109163 in mod_vhost_alias).

Two teams found it independently. Anthropic’s OSS Scanner reported it on October 26, and Anthony Weems and Simon Scannell from Google Cloud Vulnerability Research reported it on November 3. More on what the AI part means for you further down.

Is it being exploited? Wiz’s write-up said there was no public exploit and no exploitation in the wild when it went out on November 11. That can change fast with a bug this big, so check the CISA KEV catalog before you decide it can wait.

Which Ubuntu and Debian packages fix CVE-2026-119618

Here are the fixed apache2 versions from the Ubuntu CVE page, USN-9090-1 and the Debian security tracker. Your package needs to be this version or newer.

Release Apache base Fixed in
Ubuntu 26.10 2.4.68 2.4.68-1ubuntu6.2
Ubuntu 26.04 LTS 2.4.66 2.4.66-2ubuntu2.8
Ubuntu 24.04 LTS 2.4.58 2.4.58-1ubuntu8.19
Ubuntu 22.04 LTS 2.4.52 2.4.52-1ubuntu4.27
Ubuntu 20.04 LTS 2.4.41 2.4.41-4ubuntu3.23+esm11 (Ubuntu Pro)
Ubuntu 18.04 and older 2.4.29 and older Not affected
Debian 13 trixie 2.4.68 2.4.71-1~deb13u1 (DSA-6620-1)
Debian 12 bookworm 2.4.68 2.4.71-1~deb12u1 (DLA-4902-1)

Ubuntu fixed it on November 12 and didn’t move to 2.4.71. It patched the code inside the existing packages. Debian moved bookworm and trixie to 2.4.71. Same result, different version strings, which is exactly why “upgrade to 2.4.71” is the wrong check on Ubuntu.

The Ubuntu 22.04 trap: 2.4.52 is still affected

Upstream says 2.4.55 through 2.4.70. Ubuntu 22.04 reports 2.4.52. So you’re fine, right? No. Ubuntu’s security team notes on the CVE page that newer versions of the HTTP/2 module were backported to the stable releases. Your Apache says 2.4.52, but the mod_http2 inside it is much newer.

You can see it in the module itself. On every Ubuntu release I tested, the patched mod_http2.so contains the version string 2.0.42. On 24.04 the unpatched release package had 2.0.22, and on 26.04 it had 2.0.35. Those are inside the affected mod_h2 range, no matter what apache2 -v says.

And here’s the part that trips people up the other way. After patching my 22.04 container, Apache still reports the same version:

Terminalbash
apache2 -v
Snippettext
Server version: Apache/2.4.52 (Ubuntu)
Server built:   2026-11-12T13:00:12

The only thing that changed is the build date. That’s why you check the package version against the table, or the changelog for the CVE ID, never the Apache version. Version checkers that ask you to paste your Apache version will get this wrong in both directions on distro packages.

Check, patch and verify on Ubuntu

Here’s the full run from the Ubuntu 22.04 container, starting from the original release package (2.4.52-1ubuntu4) with HTTP/2 turned on.

Step 1: check the package and the module.

Terminalbash
dpkg-query -W apache2
test -e /etc/apache2/mods-enabled/http2.load && echo "http2: enabled" || echo "http2: disabled"
zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz
Snippettext
apache2	2.4.52-1ubuntu4
http2: enabled
0

Step 2: prove HTTP/2 is actually served. With TLS:

Terminalbash
curl -sk -o /dev/null -w '%{http_version}\n' --http2 https://localhost/

This prints 2 when Apache negotiates HTTP/2 and 1.1 when it doesn’t. If you have a plain HTTP site, curl -sI --http2-prior-knowledge http://localhost/ tests h2c. In my container it returned HTTP/2 200.

Step 3: patch.

Terminalbash
sudo apt update
sudo apt install --only-upgrade apache2 apache2-bin apache2-data apache2-utils
dpkg-query -W apache2
zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz
Snippettext
apache2	2.4.52-1ubuntu4.27
2

The changelog now has an entry for it:

Snippettext
  * SECURITY UPDATE: mod_http2: heap corruption and RCE in assign_headers
    - debian/patches/CVE-2026-119618.patch: mod_http2: assign_headers update
      table (#975) (#977) in modules/http2/h2_request.c.
    - CVE-2026-119618

Step 4: make sure the running Apache uses the new code. This is the step people skip. In my containers there’s no systemd, so nothing restarted Apache after the upgrade, and the old module was still loaded:

Terminalbash
sudo grep -c 'mod_http2.so (deleted)' /proc/$(pgrep -o apache2)/maps
Snippettext
6

Anything above 0 means the process still has the old, deleted mod_http2.so mapped. After a full restart the same command printed 0. On a normal server with systemd the package usually restarts Apache for you, but run the check anyway. It takes a second.

Terminalbash
sudo systemctl restart apache2

Can’t patch yet? Switch HTTP/2 off

If you can’t update right now (frozen change window, a pinned package, a box someone else owns), turn HTTP/2 off. The bug lives in mod_http2, so no HTTP/2 means no attack path. Browsers fall back to HTTP/1.1 without complaining.

The cleanest way on Ubuntu and Debian:

Terminalbash
sudo a2dismod http2
sudo apachectl configtest
sudo systemctl restart apache2
curl -sk -o /dev/null -w '%{http_version}\n' --http2 https://localhost/

The last line should print 1.1. In my 24.04 test it went from 2 to 1.1, and the h2c test failed to connect over HTTP/2 at all.

The other common advice (it’s in the Wiz post too) is setting Protocols http/1.1. That works, but where you put it matters. Here’s what I saw on Ubuntu 24.04 with the module still enabled:

Where I put Protocols http/1.1 HTTP/2 over TLS
New file in conf-enabled/ Still on
Last line of apache2.conf Still on
Inside each <VirtualHost> Off
Replacing the line in mods-available/http2.conf Off

So a global “override” line didn’t win against the Protocols h2 h2c http/1.1 from the module’s own config file in my test. Either put it in every VirtualHost or just disable the module. I’d disable the module. It’s one command and easy to undo after you patch.

To find every Protocols line on a box:

Terminalbash
grep -rn '^\s*Protocols' /etc/apache2/

On a stock Ubuntu install the only hit is the module’s own http2.conf. Anything else came from you, a control panel or a Certbot tutorial.

Checking a whole fleet, read-only

If you have more than a couple of servers, put the Quick Start check in a file and run it everywhere over SSH. It only reads. It doesn’t patch, restart or change anything.

Terminalbash
cat > check-119618.sh <<'EOF'
grep PRETTY /etc/os-release
dpkg-query -W apache2
test -e /etc/apache2/mods-enabled/http2.load && echo "http2: enabled" || echo "http2: disabled"
echo "fix in changelog: $(zgrep -c CVE-2026-119618 /usr/share/doc/apache2/changelog.Debian.gz)"
grep -rhs '^\s*Protocols' /etc/apache2/
EOF

for h in web1 web2 db1; do
  echo "== $h"
  ssh "$h" 'sh -s' < check-119618.sh
done

Here’s the output of that script on my unpatched 22.04 container:

Snippettext
PRETTY_NAME="Ubuntu 22.04.5 LTS"
apache2	2.4.52-1ubuntu4
http2: enabled
fix in changelog: 0
    Protocols h2 h2c http/1.1

And after the update, fix in changelog: 2 with version 2.4.52-1ubuntu4.27. Anything that says http2: enabled and fix in changelog: 0 goes to the top of your list. If you already run agents on every box with Herdr, you can paste the same script there instead of SSHing around.

RHEL, AlmaLinux and Rocky ship mod_http2 as its own package, so check that one, not just httpd. Red Hat’s status is on its CVE page. For containers based on the official httpd Docker image, pull a 2.4.71 tag and rebuild. Updating the host does nothing for an image.

Why an AI scanner found this and what it means for patching

Anthropic’s scanner is one of two finders credited on this CVE. It’s not the first one either. VulnCheck keeps a running tracker of vulnerabilities Anthropic found, and that list keeps growing. Google found the same bug about a week later on its own. When two teams land on the same race condition in a mature module within days, I don’t expect this to be the last one.

For me that means patch speed matters more than it used to. What I’d set up on any Ubuntu web server:

  • unattended-upgrades for the security pocket, so fixes like USN-9090-1 land without you.
  • needrestart, so services still running old libraries get flagged or restarted.
  • The /proc check above, after anything security-relevant. A patched package and a patched process aren’t the same thing.
  • Livepatch doesn’t help here. It patches the kernel, not userspace like Apache.

My Linux server security guide covers the rest of the basics.

Gotchas

  • The Apache version lies on distro packages. Ubuntu 22.04 says 2.4.52 before and after the fix. Check the package version or the changelog.
  • mod_http2 2.0.42 can be patched or not. The patched Ubuntu module still reports 2.0.42. Don’t use the module version as proof either.
  • Updating isn’t the same as restarting. My containers kept the deleted module mapped until a full restart.
  • A global Protocols http/1.1 line may not win. In my test only per-VirtualHost lines or editing http2.conf worked. a2dismod http2 is simpler.
  • Ubuntu 20.04 needs Ubuntu Pro for this fix. Standard support ended, so the patched package is only in ESM.
  • Containers carry their own Apache. Rebuild images from a patched base, and don’t forget the reverse proxy in front of your app.
  • CVE-2026-119618 isn’t the only fix in this update. USN-9090-1 also patches mod_dav, mod_vhost_alias, mod_md and a CGI issue. Another reason to just take the update.

FAQ

Is Apache 2.4.52 on Ubuntu 22.04 affected by CVE-2026-119618?

Yes, if HTTP/2 is enabled and your package is older than 2.4.52-1ubuntu4.27. Ubuntu backported newer mod_http2 code into 22.04, so the upstream version range doesn’t apply.

How do I check if HTTP/2 is enabled in Apache?

Run test -e /etc/apache2/mods-enabled/http2.load && echo enabled, or sudo apache2ctl -M | grep http2. To see what the server actually negotiates, use curl -sk -o /dev/null -w '%{http_version}\n' --http2 https://localhost/.

Do I need Apache 2.4.71 on Ubuntu?

No. Ubuntu patched its existing packages instead. Install the fixed package for your release from the table above and restart Apache.

Does disabling HTTP/2 break my site?

Not for normal websites. Browsers fall back to HTTP/1.1. You might lose a bit of speed on pages with many small requests, and gRPC behind Apache needs HTTP/2, so check before you disable it there.

Is my server safe if it runs mpm_prefork?

On Ubuntu 22.04 the module’s http2.conf wraps its Protocols line in <IfModule !mpm_prefork>. On 24.04 it doesn’t. Don’t rely on your MPM. Check whether HTTP/2 is negotiated with curl and patch either way.

Your turn

Did your fleet check turn up anything? A forgotten VPS with HTTP/2 on and no updates since spring? Tell me on X at @StefanRows. And if your distro or panel does something different here, send it over and I’ll add it.

whoami

Stefan founded Ceos3c in 2016 and has spent a decade teaching cybersecurity, Linux, and web development through hands-on tutorials. He builds and ships real products while sharing his journey: ProofSwap.me, XPMetric.com, and EasyEarningsTracker.com.

More about me