CVE-2026-119618: Apache fixes critical HTTP/2 flaw

Apache has released HTTP Server 2.4.71, fixing a critical flaw in its HTTP/2 module that can let an unauthenticated attacker run code on affected servers. The flaw, tracked as CVE-2026-119618, was disclosed on 11 November 2026, and Apache rates it critical.
The bug is a race condition in mod_http2, the module that lets Apache serve HTTP/2. When several HTTP/2 streams are handled at the same time, a function called assign_headers() can write into memory shared with the connection's own thread instead of the request's own copy. Two threads changing the same structure at once corrupt the heap, and Apache says that corruption can be turned into remote code execution. The code would run with the web server's own rights, not as root, but that is still enough to read site code, configuration files and stored database passwords.
Who is affected
Apache lists HTTP Server versions 2.4.55 through 2.4.70 as affected, along with standalone mod_h2 releases 2.0.8 through 2.0.42. A server is only exposed where HTTP/2 is actually switched on, meaning mod_http2 is loaded and h2 or h2c appears in a Protocols directive. Apache's default is HTTP/1.1 only, and Red Hat states that servers offering only HTTP/1.1 are not affected. Red Hat scores the flaw at CVSS 9.8, reflecting that it needs only network access, no login and no action from a user.
The flaw was found independently by two teams: Anthropic's OSS Scanner, which reported it on 26 October, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it on 3 November. As of 12 November, no in-the-wild exploitation had been reported and the flaw was not in CISA's catalogue of known exploited vulnerabilities, although public test code showing memory corruption and crashes had appeared.
Patch now, or switch HTTP/2 off
Version 2.4.71 also fixes two smaller flaws: CVE-2026-106023, an important NULL pointer dereference in mod_md that can crash a child process, and CVE-2026-109163, a low-severity one-byte stack overwrite in mod_vhost_alias. Administrators should upgrade to 2.4.71, or install their distributor's patched package and restart Apache. Where a patch is not yet available, switching HTTP/2 off by setting Protocols http/1.1 closes the path to the critical flaw, and browsers fall back to HTTP/1.1 on their own.
Sources: Apache HTTP Server Project and Wordfence.