# Apache 2.4.71 fixes a critical HTTP/2 RCE found by Anthropic and Google: who is exposed and what to do

> CVE-2026-119618 is a race condition in mod_http2 that affects Apache HTTP Server 2.4.55 through 2.4.70 and can lead to remote code execution without authentication. There's no confirmed exploitation yet, but a crash PoC is public and HTTP/2 is common, so patch or switch HTTP/2 off now.

Published Nov 12, 2026 by TechMeasured Staff · Security · Canonical: https://techmeasured.com/security/apache-httpd-2-4-71-mod-http2-rce-cve-2026-119618-anthropic-google-found-what-to-do

**Update, November 19:** Singapore's Cyber Security Agency now says this flaw is reportedly being actively exploited. Its alert AL-2026-164 also notes a public proof of concept, according to [Cyber Security News](https://cybersecuritynews.com/apache-http-server-rce-exploitation/) and [SecurityOnline](https://securityonline.info/cve-2026-119618-apache-rce-exploited/). The two outlets date the alert November 17 and November 16 respectively. Neither reports victims, attack scale or indicators of compromise, and neither mentions a CISA KEV listing. If you haven't patched or turned off HTTP/2, treat this as urgent. If you were exposed before patching, keep and review your logs, because patching doesn't show whether a server was already hit.

The Apache HTTP Server project released **version 2.4.71 on November 11** to fix a critical bug in its HTTP/2 module. Tracked as **CVE-2026-119618**, it can let a remote attacker corrupt server memory and potentially run code. Apache's advisory says every release **from 2.4.55 through 2.4.70** is affected. So are standalone mod_h2 builds from GitHub, versions 2.0.8 through 2.0.42.

Apache is still one of the most widely deployed web servers. It runs as a front end, reverse proxy or app gateway on huge numbers of Linux hosts and inside countless container images. HTTP/2 is turned on in many of those setups. As of SecurityWeek's November 12 report, nobody has seen exploitation in the wild. But a public proof of concept already crashes servers, and Red Hat rates the flaw **CVSS 9.8**. Patch now rather than at the next maintenance window.

## What the bug is

Apache's advisory describes improper synchronization of a shared resource in mod_http2's `assign_headers()` function and says it "can lead to RCE." Ostorlab's write-up traces the root cause. On a request with a Content-Type but no body and no Content-Length, one code path writes a synthetic Content-Length header into a header table shared between threads instead of the per-request copy. Those tables aren't thread-safe. Many concurrent bodyless requests over one HTTP/2 connection can therefore race and corrupt the heap. The fix changes that single write.

Results depend on timing, load and memory layout. They range from crashed worker processes (denial of service) to, per Red Hat's description cited by SecurityWeek, unauthenticated command execution as the Apache user.

**Only servers with HTTP/2 enabled (`h2` or `h2c`) are affected.** HTTP/1.1-only servers are not.

## Who found it

Apache credits two independent reports:

| Reporter | Reported to Apache |
|---|---|
| Anthropic's OSS Scanner (internal ID ANT-2026-MAPKT6MZ) | October 26, 2026 |
| Anthony Weems and Simon Scannell, Google Cloud Vulnerability Research | November 3, 2026 |

That puts a fix out 16 days after the first report. It's another example of AI-assisted scanners turning up serious bugs in core open-source infrastructure, with human researchers landing on the same bug days later.

## Exposure and exploit status

- **In the wild:** none reported at first, according to SecurityWeek and SecurityOnline, and Ostorlab noted the CVE was not in CISA's Known Exploited Vulnerabilities catalog as of November 12. That changed in mid-November, when Singapore's CSA said the flaw was reportedly being exploited (see the update above).
- **Public code:** SecurityWeek says a GitHub proof of concept reproduces memory corruption and crashes but doesn't demonstrate code execution. Red Hat says public research has shown a reliable exploit, but SecurityWeek notes it doesn't identify that research.
- **Footprint:** Cloud security firm Wiz, as cited by SecurityWeek, found affected versions in **64% of cloud environments** and publicly exposed instances in **51%**. Wiz cautions that these figures ignore configuration, so they aren't a count of exploitable servers.

## Two smaller fixes in the same release

| CVE | Module | Apache severity | Affected | Effect |
|---|---|---|---|---|
| CVE-2026-106023 | mod_md (ACME certificates) | Important | 2.4.30–2.4.70 | NULL pointer dereference crashes a child process |
| CVE-2026-109163 | mod_vhost_alias | Low | 2.4.69–2.4.70 | One-byte stack buffer overwrite, a follow-up to CVE-2026-63292 |

## What to do

**1. Find out whether you run HTTP/2.** These checks come from Ostorlab's guide:

```
# Debian/Ubuntu
apache2 -v
apache2ctl -M | grep http2

# RHEL/Fedora
httpd -v
httpd -M | grep http2
rpm -q mod_http2        # on RHEL, check the module package, not the httpd version

# Is h2/h2c in Protocols?
grep -R "Protocols" /etc/apache2 /etc/httpd 2>/dev/null
```

**2. Upgrade.** Move to 2.4.71 or your distribution's patched package, then restart Apache:

```
sudo apt update && sudo apt install --only-upgrade apache2   # Debian/Ubuntu
sudo dnf update httpd mod_http2                              # RHEL/Fedora
```

Distro packages often backport fixes without changing the version number. Check your vendor's advisory rather than relying on `-v` output alone. Ostorlab says RHEL 8 and earlier aren't affected and lists fixed mod_http2 packages for RHEL 9 and 10. **Rebuild any container images that bundle Apache.** Pulling a new base image isn't enough until the image is rebuilt and redeployed.

**3. If you can't patch today, turn HTTP/2 off.** That removes the vulnerable code path at some cost to performance. On Debian/Ubuntu, run `sudo a2dismod http2` and restart. On RHEL/Fedora, comment out `LoadModule http2_module` and remove `h2`/`h2c` from `Protocols`, then restart. Confirm that the `-M | grep http2` check returns nothing.

**4. Don't count on application-layer patches.** SecurityWeek notes Wordfence's warning that WordPress updates can't fix this, because the flaw sits in the web server underneath. Managed hosting customers should ask their provider whether 2.4.71 or a backport is deployed.

**5. Look for signs of trouble.** Ostorlab suggests searching error logs for segfaults and unexpected child exits (`grep -Ei "segfault|signal 11|AH00051"`) and listing core dumps with `coredumpctl`. A burst of crashes on an affected HTTP/2 server is a lead worth preserving, not proof of compromise.

## What to watch

With exploitation now reported by Singapore's CSA, watch for CISA to add the CVE to its exploited list and for a working code-execution exploit to go public. Also expect follow-on fixes from appliance and hosting vendors that embed Apache 2.4.55 or later.


## Sources

1. [Apache HTTP Server Project — Apache HTTP Server 2.4 vulnerabilities](https://httpd.apache.org/security/vulnerabilities_24.html)
2. [SecurityWeek — Apache Patches Critical HTTP Server RCE Found by Anthropic, Google](https://www.securityweek.com/apache-patches-critical-http-server-rce-found-by-anthropic-google/)
3. [Ostorlab — Apache HTTP Server HTTP/2 RCE, Fixed in 2.4.71 (CVE-2026-119618)](https://blog.ostorlab.co/apache-http-server-http2-rce-cve-2026-119618.html)
4. [SecurityOnline — CVE-2026-119618: Apache HTTP Server Remote Code Execution Fixed in 2.4.71](https://securityonline.info/apache-http-server-cve-2026-119618-rce-fixed/)
5. [Cyber Security News — Critical Apache HTTP Server RCE Vulnerability Actively Exploited in Attacks](https://cybersecuritynews.com/apache-http-server-rce-exploitation/)
6. [SecurityOnline — CVE-2026-119618: Apache HTTP Server RCE Actively Exploited, Patch Now](https://securityonline.info/cve-2026-119618-apache-rce-exploited/)
