Apache HTTP Server versions 2.4.55 through 2.4.70 have a race in the HTTP/2 module that can corrupt heap memory and lead to remote code execution. Apache fixed CVE-2026-119618 in 2.4.71 on November 11. Operators of internet-facing Apache servers should check the running build and negotiated protocol on each endpoint before closing out the fix.
The CVE record names mod_http2 and its assign_headers() function. Apache describes the issue as concurrent execution against a shared resource with improper synchronization that “can lead to RCE.” A reachable, affected server handling HTTP/2 traffic is the exposure to prioritize; a compromised web-server process would have the privileges assigned to that process.
Shared headers meet concurrent threads
HTTP/2 lets a single connection carry concurrent streams. In this case, threads handling shared resources in assign_headers() can race, and the resulting heap corruption creates a path to code execution. Wiz Research describes the possible attacker as remote and unauthenticated. Wiz reported no exploit available and no observed exploitation when it published on November 11.
Apache lists affected HTTP Server releases from 2.4.55 through 2.4.70; it also lists standalone GitHub mod_h2 releases from 2.0.8 through 2.0.42. For standalone builds, Wiz advises moving to a release newer than 2.0.42. Check the actual packaged module and vendor backport status where a distribution uses its own versioning, alongside the upstream version range.
Wiz found resources it classified as vulnerable in 64% of cloud environments and publicly exposed instances in 51% of environments; its measurement did not account for configuration. Check each server’s running build and active HTTP/2 configuration to determine its exposure.
Inventory the live HTTP/2 path
Start with the Apache front ends that terminate traffic for public sites and APIs. Record the installed and running HTTP Server build, the loaded mod_http2 module, and the effective Protocols setting, including virtual-host overrides. A loaded module by itself is weaker exposure evidence than a client actually negotiating h2 or h2c with an affected host. If a proxy terminates HTTP/2 upstream, check which protocol reaches Apache before assigning that origin the same exposure.
Pair your asset inventory with a client-side protocol negotiation check against each affected endpoint. Record the negotiated protocol and the process or container image version that served the connection. Use access logs and server telemetry to investigate unexpected child-process crashes or restarts in context, rather than treating those events as a fingerprint for this CVE.
Upgrade Apache and verify negotiation
Upgrade affected HTTP Server deployments to 2.4.71 or a vendor build that explicitly carries the fix. Rebuild container images and restart or replace running instances, so the process serving requests uses the patched binary. If the upgrade must wait, Wiz recommends restricting Apache to HTTP/1.1 by removing h2 and h2c from the effective configuration; the Protocols http/1.1 directive is its example. Apply the change to the affected listener and virtual hosts, validate the configuration, and reload the service.
After the rollout, query the deployed build again and negotiate a fresh connection to each public endpoint. The patched path should report 2.4.71 or an explicitly fixed vendor build; the temporary mitigation should negotiate HTTP/1.1 instead of HTTP/2 at the Apache listener. Keep the test tied to the running process: a corrected file on disk does little for a worker still serving the old binary.