News Vulnerabilities & Zero-Days

Apache HTTP Server patches critical mod_http2 race condition that can lead to remote code execution

The Apache Software Foundation fixed a concurrency flaw in mod_http2 that it rates critical and says can lead to RCE. Only servers with HTTP/2 enabled are exposed, so inventory is the first job.

Published
Banner showing an Apache feather over a cracked HTTP/2 frame, with the headline about the critical mod_http2 race condition.

Key takeaways

  • Apache rates CVE-2026-119618 in mod_http2 critical and says it can lead to remote code execution.
  • Only servers that load mod_http2 and enable h2 or h2c via the Protocols directive are exposed.
  • The Apache advisory gives no CVSS score; the critical numeric rating comes from Red Hat.
  • Red Hat and Wiz disagree on whether a working exploit exists, so patch as if one does.
  • Standalone mod_h2 has no fixed release, so removing h2 and h2c from Protocols is the only mitigation there.

The Apache Software Foundation shipped a new HTTP Server release this week that fixes CVE-2026-119618, a flaw in the mod_http2 module. Apache describes it as a "Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server's mod_http2 in assign_headers() can lead to RCE" and rates it critical. The advisory lists the affected range of httpd releases and of the standalone mod_h2 module; check your build against it rather than assuming.

Apache credits Anthropic's OSS Scanner, which reported the bug in late October, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research, who reported it independently in early November.

Who is exposed #

The bug is reachable before authentication by any client that can negotiate HTTP/2, whether over TLS (h2) or in cleartext (h2c). Only servers that load mod_http2 and enable it through the Protocols directive are affected. That is a smaller set than every httpd install, but the only way to know which set you are in is to check the Protocols directive on every instance, including containers.

The Apache advisory assigns no CVSS score. Red Hat rates the flaw critical with a near-maximum score; that is Red Hat's figure, not Apache's.

Exploitation status is contested. Red Hat states that public research has demonstrated a reliable exploit against a default configuration. Wiz, quoted by The Hacker News, said no exploit was available and no in-the-wild exploitation had been reported. Treat the reports as conflicting and patch on the assumption that a working exploit exists.

Same release, two more fixes #

The release also closes CVE-2026-106023, a NULL pointer dereference in mod_md that Apache rates important, and CVE-2026-109163, a low-severity stack-based buffer overflow in mod_vhost_alias.

What to do #

  • Patch to the newest httpd release or your distribution's backport. Include containers and base images.
  • Where patching lags, remove h2 and h2c from the Protocols directive. Apache lists no official workaround; this mitigation comes from Wiz via The Hacker News. Check the server-wide setting and every virtual host, because a VirtualHost block can re-enable the protocol on its own.
  • Standalone mod_h2 users have no fixed release to install. The Hacker News reports the project's GitHub release list stops before the fix and the repository has been archived read-only since June. The Protocols change is the only option there.

Sources

  1. Apache HTTP Server 2.4 vulnerabilities, Apache Software Foundation
  2. Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely, The Hacker News

Questions this raises

Is my Apache server affected if HTTP/2 is not enabled?
No. The flaw is in mod_http2 and is only reachable when the module is loaded and the Protocols directive enables h2 or h2c. Check both the global configuration and every VirtualHost block.
Is there a workaround if I cannot patch immediately?
Apache lists none. Wiz, via The Hacker News, advises removing h2 and h2c from the Protocols directive so clients fall back to the older HTTP protocol.
Is it being exploited?
Reports conflict. Red Hat says public research demonstrated a reliable exploit against a default configuration, while Wiz said no exploit was available and no in-the-wild exploitation had been reported.

apachehttpdhttp2