Apache HTTP/2 Flaw CVE-2026-119618: Update to 2.4.71 Now
Share: https://www.ellixorlabs.com/blog/apache-http2-flaw-cve-2026-119618-update-2-4-71 (copy URL for iMessage or social)
Published (display in IST)
Updated (IST)

A critical bug in Apache's HTTP/2 module could let attackers run code on web servers. Here is how to check if your site is affected and what to do today.
Apache has released version 2.4.71 of its HTTP Server to fix a critical flaw in its HTTP/2 module that could let a remote attacker run code on a web server. The bug, tracked as CVE-2026-119618, affects Apache 2.4.55 to 2.4.70 and was fixed on 11 November 2026, according to the Apache security advisory. Any business running Apache with HTTP/2 switched on, whether on its own server or through a hosting provider, should update now. Security firm Wiz says a remote attacker needs no login to attempt the attack, although it had seen no public exploit or attacks at the time of writing.
What is the Apache HTTP/2 flaw and who found it?
The problem sits in mod_http2, the part of Apache that handles HTTP/2, the newer web protocol that browsers use to load pages more efficiently. Apache describes it as a race condition: when two threads touch the same data in a function called assign_headers() without proper coordination, memory on the server can be corrupted, and that corruption can be used to run commands with the web server's privileges. Apache credits two independent discoveries, one by Anthropic's automated open source scanner, reported on 26 October, and one by Anthony Weems and Simon Scannell of Google Cloud's vulnerability research team, reported on 3 November. Standalone builds of the mod_h2 module from GitHub, versions 2.0.8 to 2.0.42, carry the same bug. Wiz estimates that 64% of the cloud environments it monitors contain a vulnerable Apache version and 51% have one exposed to the internet, a figure it notes does not account for whether HTTP/2 is actually switched on.
How do I check if my server is affected?
You need two answers: which Apache version you run, and whether HTTP/2 is on. Running httpd -v (or apache2ctl -v on Debian and Ubuntu) prints the version. Then look in your configuration for a Protocols directive that lists h2 or h2c. Apache's documentation says the default is http/1.1 only, so HTTP/2 is exposed only where someone has turned it on. If you use shared or managed hosting and cannot see these files, ask your host directly whether its Apache servers run 2.4.71 or a patched package. Sites served by Nginx, LiteSpeed or a hosted platform that does not use Apache are not affected by this particular bug.
What should website owners do today?
Upgrade to Apache 2.4.71, which the Apache project announced on 11 November as the best available 2.4 release. Many servers get Apache from their Linux distribution rather than from the Apache project directly, so watch your distribution's security notices: on 12 November, Debian's security tracker listed the apache2 packages for its stable releases as still vulnerable, with a fixed 2.4.71 package only in its unstable branch. Distributions often patch older version numbers, so trust the security notice, not the version string alone. If you cannot patch quickly, Wiz suggests limiting the Protocols line to http/1.1 as a temporary step, then reloading Apache. The same release also fixes CVE-2026-106023, rated important, which can crash Apache worker processes through the mod_md certificate module in versions 2.4.30 to 2.4.70, and a low severity mod_vhost_alias bug in 2.4.69 and 2.4.70. For more on recent server patches, see our reports on the actively exploited WordPress core flaw and the critical OpenSSH flaw on Alpine Linux.
Frequently asked questions
Is my website affected by the Apache CVE-2026-119618 flaw? Only if it runs on Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2 switched on through the Protocols directive (h2 or h2c). Sites served by other web servers such as Nginx are not affected by this bug. On managed hosting, ask your provider to confirm its servers are patched.
Can I turn off HTTP/2 instead of updating Apache? Only as a stopgap. Removing h2 and h2c from the Protocols directive so that only http/1.1 remains takes away the vulnerable HTTP/2 code path, which is the temporary mitigation Wiz recommends. It is not a fix, so install Apache 2.4.71 or a patched package from your Linux distribution as soon as you can.
Is CVE-2026-119618 being exploited by attackers? Wiz said on 11 November 2026 that no exploit was publicly available and it knew of no attacks in the wild. Apache still rates the flaw critical because a remote attacker could potentially run code on the server, so patch now rather than waiting for reports of attacks.
If you are not sure how your website or web application is hosted, or who is responsible for patching it, talk to our team. We build and maintain web applications and can help you set up a simple routine for applying security updates like this one.
FAQ
Is my website affected by the Apache CVE-2026-119618 flaw?
Only if it runs on Apache HTTP Server 2.4.55 to 2.4.70 with HTTP/2 switched on through the Protocols directive (h2 or h2c). Sites served by other web servers such as Nginx are not affected by this bug. On managed hosting, ask your provider to confirm its servers are patched.
Can I turn off HTTP/2 instead of updating Apache?
Only as a stopgap. Removing h2 and h2c from the Protocols directive so that only http/1.1 remains takes away the vulnerable HTTP/2 code path, which is the temporary mitigation Wiz recommends. It is not a fix, so install Apache 2.4.71 or a patched package from your Linux distribution as soon as you can.
Is CVE-2026-119618 being exploited by attackers?
Wiz said on 11 November 2026 that no exploit was publicly available and it knew of no attacks in the wild. Apache still rates the flaw critical because a remote attacker could potentially run code on the server, so patch now rather than waiting for reports of attacks.
Talk to Ellixor Labs about this topic.
Source: Apache Software Foundation