$RodHat_/search
MOTD

Apache httpd 2.4.71: mod_http2 RCE, CVE-2026-119618

Published by

This article may contain Amazon affiliate links. I may earn a commission if you buy through them. Disclosure.

Editorial card for the Apache httpd mod_http2 vulnerability
Editorial card: RodHat

The Apache HTTP Server project shipped 2.4.71 on November 11 to fix CVE-2026-119618, a race condition in mod_http2 that corrupts heap memory and can lead to remote code execution. The Apache advisory rates it critical. It affects httpd 2.4.55 through 2.4.70, and the standalone mod_h2 from GitHub, 2.0.8 through 2.0.42.

The bug is in assign_headers(). The NVD text calls it “Concurrent Execution using Shared Resource with Improper Synchronization.” Translated out of CWE-speak: HTTP/2 multiplexes lots of requests over one connection, the module handles them on multiple threads, and two threads are touching memory without proper locking. Heap corruption follows. Anyone who has debugged a threaded C program at 3am knows how this ends.

NVD’s secondary-source score is CVSS 3.1 8.1 (AV:N/AC:H/PR:N/UI:N), high complexity because you have to win a race. Don’t let the “high” in “attack complexity” calm you down. The reporters were Anthropic’s OSS Scanner (reported October 26) and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research (November 3). The fix landed in 2.4.x on November 11, same day as the release.

The condition that matters: this only bites if HTTP/2 is on. BleepingComputer says that’s off by default, and watchTowr’s advice is “patch now or drop h2 until you can.” So the fast mitigation is boring. Check your Protocols directive:

grep -rn "Protocols" /usr/local/etc/apache24/ /etc/apache2/ /etc/httpd/ 2>/dev/null
httpd -v
httpd -M | grep http2

If Protocols lists h2 or h2c and httpd -M shows http2_module, you’re in scope. Remove h2/h2c from Protocols, restart, and you’re back on HTTP/1.1 until you can upgrade to 2.4.71. Package maintainers backport, so check your vendor’s changelog rather than trusting the version string alone.

Wiz telemetry, as relayed by BleepingComputer, says 64% of cloud environments have vulnerable resources and about half of those are publicly exposed, with the caveat that this doesn’t account for whether h2 is actually enabled. Wiz also says it knows of no public exploits or attacks yet. That sentence has a shelf life measured in days.

2.4.71 also carries two other fixes: CVE-2026-106023, a NULL dereference in mod_md that crashes a child process (rated important), and CVE-2026-109163, a one-byte stack overwrite in mod_vhost_alias (low) that only affects 2.4.69 and 2.4.70. The mod_vhost_alias one is a follow-up to CVE-2026-63292 from the 2.4.69 release. Fixing a stack overflow and leaving an off-by-one behind is a tradition older than most of the people filing these CVEs.

Opinion, since you came here for it: HTTP/2 inside the web server process is a lot of threaded parsing code sitting in the same address space as your config and your TLS keys. I’d still put a dumb, small thing in front. If you want the sandboxing angle, the sandboxing hub has the ways to cut a daemon’s privileges down so a bug like this buys less, and the kernel and security hub has the rest of the week, including the ScreenConnect worm and the Chrome zero-day. Check your Protocols line. Then upgrade.

Sources

  1. CVE-2026-119618 (NIST National Vulnerability Database)
  2. Apache HTTP Server 2.4 vulnerabilities (The Apache HTTP Server Project)
  3. Apache HTTP Server patches critical HTTP/2 remote code execution flaw (BleepingComputer)