Apache HTTP Server 2.4.71, released November 11, 2026, fixes CVE-2026-119618, a critical memory-corruption flaw in mod_http2 that can lead to remote code execution. For small businesses and government contractors, the immediate task is to find the Apache instances actually processing HTTP/2—not simply the public-facing product name—and verify that the serving process receives the fix.
What is verified
Apache identifies an improperly synchronized shared-resource operation in assign_headers(). Its advisory lists HTTP Server 2.4.55 through 2.4.70 as affected and includes the fix in 2.4.71. Apache credits independent reports from Anthropic’s OSS Scanner and Google Cloud Vulnerability Research; the reports reached its security team on October 26 and November 3, respectively. Those discovery dates are distinct from the November 11 fixed release.
Wiz describes an unauthenticated remote attack against HTTP/2 handling that could corrupt heap memory and execute code with the web-server process’s privileges. That is a serious server-control risk, but not automatically root access. What an attacker could reach afterward would depend on that process’s files, credentials, network connections and cloud permissions.
Source: Apache HTTP Server original security advisory and release timeline.
Source: Wiz original exposure analysis and mitigation guidance, November 11.
Find the vulnerable protocol path
The relevant combination is an affected server or module build and enabled HTTP/2 processing. A version inventory is the starting point, not proof that every listed instance is remotely exploitable. Wiz explicitly says its cloud prevalence figures do not account for configuration; they should not be read as the share of environments with a confirmed exploitable HTTP/2 endpoint.
Trace traffic through your CDN, load balancer, reverse proxy and origin. HTTP/2 on the browser-facing connection does not by itself establish HTTP/2 at Apache behind it. Conversely, a protected public hostname does not settle whether an origin or internal listener can be reached another way. Ask the hosting provider or managed service provider which component terminates each protocol, which package supplies mod_http2, and who owns the change.
Actions for lean security teams
- Inventory the running service. Identify Apache instances, containers, virtual machines and packaged appliances that use the affected HTTP Server range. Include internal services and separately maintained module builds. Record the service owner, package source, HTTP/2 configuration and reachable listeners.
- Deploy the verified fix. Upgrade upstream Apache HTTP Server to 2.4.71 or later, or obtain explicit confirmation that your distribution or appliance vendor has backported this CVE’s fix. A lower displayed upstream version is not conclusive evidence either way when vendor backports are involved. Replace or restart serving processes as required by your supported rollout procedure, and update base images so replacement instances do not restore the vulnerable build.
- If patching must wait, remove the HTTP/2 path. Wiz recommends temporarily disabling HTTP/2, restricting active protocols to HTTP/1.1 and removing h2 and h2c references. Review the effective configuration across virtual hosts and included files, test compatibility, apply the supported service change, and verify the actual listeners no longer negotiate the disabled protocol. Keep an owner and deadline for patching; a temporary protocol change is not a software fix.
- Reduce the authority behind the server. Review service-account privileges, application-secret access and unnecessary outbound or internal connectivity. This does not repair the memory flaw, but it can limit the consequences of a compromised worker.
- Preserve and review evidence proportionately. Retain access, error, endpoint and network logs. Investigate unexplained worker crashes, unusual child processes or unexpected outbound connections in context. These are investigation leads, not CVE-specific proof of exploitation.
Limits that matter
Wiz’s November 11 report said no public exploit was available and no in-the-wild exploitation had been reported at its publication time. That is a time-bounded statement, not proof that exploitation cannot occur or a current guarantee that no attacks exist. The reviewed sources do not establish an active campaign or support attributing this flaw’s use to any country.
Apache also lists standalone GitHub mod_h2 releases 2.0.8 through 2.0.42 as affected. Wiz’s table and prose disagree about the standalone fixed boundary. We therefore do not recommend a specific standalone fixed version here: administrators of those builds should obtain an unambiguous upstream or supplier fix confirmation, or disable the affected HTTP/2 path while that is resolved. The Apache HTTP Server 2.4.71 fix is independently clear in the vendor advisory.
Bulwark assessment
Treat this as a prioritized server patch and configuration-verification job, not as evidence that your organization has already been breached. A useful closure record names the affected instances, the vendor-confirmed fixed package, the running deployment that consumed it and the protocol checks performed afterward. For outsourced hosting, ask for that evidence rather than accepting only a statement that the website is behind a firewall. If your own telemetry indicates compromise, preserve evidence and assess the credentials and systems the worker could reach separately from installing the patch.

