- SMB/SME
- Enterprise
· Updated · ASC Editorial Team
Apache's HTTP/2 Flaw Is Reportedly Being Exploited: Check Your Web Servers
On 11 November 2026, the Apache Software Foundation released Apache HTTP Server 2.4.71. It fixes CVE-2026-119618, a flaw in mod_http2, the module that handles HTTP/2 connections. Apache rates it critical: a timing flaw can corrupt the server's memory and lead to remote code execution. It affects versions 2.4.55 to 2.4.70, and only where mod_http2 is enabled. The separate mod_h2 module is affected from version 2.0.8 to 2.0.42.
On 17 November, Singapore's Cyber Security Agency (CSA) issued an alert saying the flaw "is reportedly being actively exploited", and that proof-of-concept exploit code is publicly available. CSA hasn't said who saw the attacks or how many servers were hit, and other authorities haven't yet confirmed exploitation. But public exploit code and a national warning are reason enough to act now.
Apache HTTP Server runs a large share of the world's websites, customer portals and reverse proxies. It is also built into many commercial products and appliances, where it doesn't show up as "Apache" in an asset list. Those copies are fixed when the product's vendor ships an update, not when you patch your servers.
Version numbers can mislead in both directions. Linux distributions often backport the fix into their own packages without changing the version to 2.4.71, so a server reporting an older version may already be fixed. A server that hasn't had its distribution's update is still exposed, however recently it was built. Check against your distribution's advisory, not the version string alone.
Three steps follow.
First, find every Apache server, including those in products you bought, and check whether HTTP/2 is enabled on each one.
Second, install 2.4.71 or your distribution's fixed package. For products with Apache built in, ask the vendor whether they're affected and when a fix is due. Apache says only servers with mod_http2 enabled are affected. If you can't patch straight away, turning HTTP/2 off removes that exposure until you can.
Third, treat any internet-facing server that ran an affected version with HTTP/2 on as possibly compromised, and check it. Look for unexpected processes, new files in web directories and unusual outbound connections.
If you rely on a firewall's intrusion prevention to buy time, check that a signature for this flaw exists. Fortinet published one on 12 November, IPS signature 60872. Check Point listed the flaw in its weekly threat report on 16 November without naming a protection, and Palo Alto Networks had published nothing on it by 20 November. If you use either, ask rather than assume.
Do you know which of your web servers, and which of the products you've bought, run Apache with HTTP/2 turned on?
Get Insights by email
A short round-up of new articles every Monday morning. Nothing else.