The Apache Software Foundation released Apache HTTP Server 2.4.71 on 11 November. The most serious fix is for CVE-2026-119618, a race condition in the HTTP/2 module (mod_http2) that can corrupt memory and lead to remote code execution. It is rated 8.1 under CVSS.
Who is affected
- Apache HTTP Server 2.4.55 to 2.4.70 with mod_http2 enabled, which is common on modern web servers and hosting platforms
- Standalone mod_h2 builds 2.0.8 to 2.0.42
The release also fixes a crash in mod_md, which manages automatic certificates (CVE-2026-106023, versions 2.4.30 to 2.4.70), and a low-risk memory flaw in mod_vhost_alias (CVE-2026-109163).
The HTTP/2 flaw was found by Anthropic’s open-source scanning project and by researchers at Google Cloud. As of 11 November, there were no reports of exploitation or public exploit code.
Why act now
Recent weeks have shown how quickly attackers move once details of a web server flaw are public. PHP2Shell exploit attempts reached the millions within a day. AI-assisted tools are also shortening the time between a fix being published and working exploits appearing, so “no known attacks” rarely lasts long.
What to do
- Update to 2.4.71, or to your Linux distribution’s patched package, and restart Apache.
- Check appliances and hosting panels that bundle Apache, as they may need a vendor update.
- If you cannot patch immediately, disable mod_http2 (and mod_md if you do not use it) as a temporary workaround. Sites will fall back to HTTP/1.1.
- Put a web application firewall in front of public sites, and keep its rules current.
Sources: SecurityOnline: Apache HTTP Server CVE-2026-119618 fixed; Red Hat: CVE-2026-119618.