---
title: "Apache httpd 2.4.71 Fixes Critical mod_http2 RCE"
url: https://erroneo.us/security/briefs/apache-httpd-mod-http2-rce-cve-2026-119618/
description: "CVE-2026-119618: a race in mod_http2 can corrupt heap memory and lead to RCE in Apache httpd 2.4.55-2.4.70 with HTTP/2 enabled. Upgrade to 2.4.71 this week."
type: security-brief
section: "Security Digest"
date_published: 2026-11-11
date_modified: 2026-11-12
publisher: erroneo.us
author: erroneo.us Security Desk
verdict: "Patch this week"
cves: ["CVE-2026-119618", "CVE-2026-106023", "CVE-2026-109163"]
severity: "critical"
exploited: "none-known"
kev: false
license: All rights reserved. Quote with attribution and a link.
---

# Apache httpd 2.4.71 Fixes Critical mod_http2 RCE

**Verdict: Patch this week.** Apache rates this critical and it needs no authentication, but it only applies when HTTP/2 is enabled, there is no public exploit, and switching to HTTP/1.1 removes the exposure until you can upgrade.

- **Who must act:** Anyone running Apache HTTP Server 2.4.55 through 2.4.70 with h2 or h2c in a Protocols directive, especially on internet-facing hosts and in container images built before November 11, 2026.
- **Who can relax:** Servers that only speak HTTP/1.1, servers on 2.4.54 or earlier, and RHEL 8 and earlier, which Red Hat lists as not affected.
- **Affected:** Apache HTTP Server 2.4.55 through 2.4.70 with HTTP/2 enabled; Standalone mod_h2 2.0.8 through 2.0.42
- **Fixed:** Apache HTTP Server 2.4.71; Debian trixie apache2 2.4.71-1~deb13u1 (DSA-6620-1)
- **CVEs:** CVE-2026-119618, CVE-2026-106023, CVE-2026-109163
- **CISA KEV:** no · **Exploitation:** No known exploitation

## What to do

1. Check the version with httpd -v or apachectl -v; 2.4.55 through 2.4.70 is in range.
2. Check whether HTTP/2 is on: apachectl -M | grep http2, then search the configuration for Protocols lines that list h2 or h2c, including per virtual host.
3. Upgrade to Apache HTTP Server 2.4.71 or your distribution's fixed package and restart.
4. If you cannot upgrade yet, set Protocols http/1.1 everywhere it is defined (or a2dismod http2 on Debian and Ubuntu) and restart.
5. Rebuild and redeploy container images based on httpd that were built before November 11, 2026.

### How to check if you are affected

- Run httpd -v (or apache2 -v) on hosts and inside images to find versions 2.4.55 through 2.4.70.
- Run grep -Rni 'Protocols' /etc/apache2 /etc/httpd to find virtual hosts that enable h2 or h2c.
- No indicators of compromise have been published; watch the error log for unexplained child process crashes (segmentation faults) as a general signal of memory corruption attempts.

## What happened

On November 11, 2026, the Apache HTTP Server Project released version 2.4.71, which fixes three vulnerabilities. The one that matters is CVE-2026-119618, which [Apache rates critical](https://httpd.apache.org/security/vulnerabilities_24.html) and titles "mod_http2: heap corruption and RCE in assign_headers".

The flaw is a race condition. Apache describes it as "Concurrent Execution using Shared Resource with Improper Synchronization" in the `assign_headers()` function of mod_http2 that "can lead to RCE". [Red Hat's analysis](https://access.redhat.com/security/cve/cve-2026-119618) puts it more concretely: a thread-safety flaw lets one worker thread write into memory owned by the connection thread, corrupting server memory.

Two parties found it independently. Anthropic's OSS Scanner reported it on October 26, 2026, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it on November 3. The fix landed in the 2.4.x branch as commit 824beab on the release day.

The same release fixes two smaller issues: CVE-2026-106023, an "important" NULL pointer dereference in mod_md that crashes a child process (2.4.30 through 2.4.70), and CVE-2026-109163, a "low" one-byte stack overwrite in mod_vhost_alias (2.4.69 and 2.4.70).

## Who is affected

Apache HTTP Server 2.4.55 through 2.4.70, and the standalone mod_h2 module from GitHub versions 2.0.8 through 2.0.42. Red Hat states that only servers with HTTP/2 enabled, meaning `h2` or `h2c` in a `Protocols` directive, are affected, and that servers serving only HTTP/1.1 are not.

Distribution status as of November 12, 2026:

- **Debian:** the [security tracker](https://security-tracker.debian.org/tracker/CVE-2026-119618) shows trixie fixed in 2.4.71-1~deb13u1 under DSA-6620-1 and unstable fixed in 2.4.71-1. Bookworm was still listed as vulnerable when checked.
- **Red Hat:** RHEL 8 and earlier are not affected. RHEL 9 and 10 are rated Important instead of Critical, because each HTTP/2 stream there gets its own allocator, which makes exploitation harder. Errata status was not confirmed.
- **Standalone mod_h2:** the [GitHub releases page](https://github.com/icing/mod_h2/releases) still showed v2.0.42 as the newest release, with no mention of the CVE. A fixed standalone release is not confirmed as of November 12, 2026.

## Do you really need to act?

Yes, if HTTP/2 is on. It is a remote, pre-authentication memory corruption bug in one of the most widely deployed web servers, and Apache itself uses the word RCE. Red Hat scores it 9.8 (CVSS 3.1). Apache and the CVE record publish no score.

The reasons not to panic are real, though:

- **HTTP/2 must be enabled.** Many Apache installs sit behind a load balancer or CDN that terminates HTTP/2 and speaks HTTP/1.1 to the origin. Those origins are not exposed to this bug unless the origin's own configuration enables h2 or h2c.
- **It is a race.** Turning a concurrency bug into reliable code execution is harder than exploiting a straightforward overflow. A crash is the more likely first outcome.
- **No exploit is known.** [Wiz reported](https://www.wiz.io/blog/cve-2026-119618-rce-apache-http-server-vulnerability) no public exploit and no exploitation in the wild as of November 11, and the CVE is not in CISA's KEV catalog (version 2026.11.10).

Wiz also says 64% of cloud environments it sees contain vulnerable versions and 51% have them publicly exposed, but notes those figures ignore configuration, so they overstate how many actually have HTTP/2 on. The fix commit is public, which is where exploit development usually starts. Plan the upgrade this week, and sooner for internet-facing servers.

## What to do now

1. Find the version: `httpd -v` or `apachectl -v` (`apache2 -v` on Debian and Ubuntu).
2. Find out whether HTTP/2 is enabled: `apachectl -M | grep http2`, then `grep -Rni 'Protocols' /etc/apache2 /etc/httpd`. Check every virtual host; `Protocols` can be set per vhost.
3. Upgrade to 2.4.71 or the fixed distribution package, then restart the server.
4. If the upgrade has to wait, restrict the server to HTTP/1.1 with `Protocols http/1.1`, or on Debian and Ubuntu run `a2dismod http2 && systemctl restart apache2`. Apache publishes no official workaround; this follows from Red Hat's statement that HTTP/1.1-only servers are not affected.
5. Rebuild container images that include httpd and were built before November 11.

Disabling HTTP/2 does nothing for the mod_md and mod_vhost_alias fixes, so it is a stopgap, not a substitute.

## How to tell if you were hit

Neither Apache nor any source reviewed has published indicators of compromise, and no exploitation has been reported. Failed attempts against a memory corruption bug typically crash the child process, so repeated segmentation fault notices in the error log on an HTTP/2-enabled server are worth a look. That is a general signal, not a published indicator for this CVE.

## Timeline

- Oct 26, 2026 — Anthropic's OSS Scanner reports the flaw to the Apache security team.
- Nov 3, 2026 — Google Cloud Vulnerability Research reports it independently.
- Nov 11, 2026 — Fix committed; Apache HTTP Server 2.4.71 released; [announced on oss-security](https://www.openwall.com/lists/oss-security/2026/11/11/13); CVE record published.
- Nov 12, 2026 — Debian trixie fixed via DSA-6620-1; no exploitation reported.

## Sources

1. [Apache HTTP Server Project — Apache HTTP Server 2.4 vulnerabilities (fixed in 2.4.71)](https://httpd.apache.org/security/vulnerabilities_24.html)
2. [CVE.org — CVE-2026-119618](https://www.cve.org/CVERecord?id=CVE-2026-119618)
3. [oss-security — CVE-2026-119618: Apache HTTP Server: mod_http2: heap corruption and RCE in assign_headers](https://www.openwall.com/lists/oss-security/2026/11/11/13)
4. [Apache HTTP Server Project — CHANGES_2.4.71](https://downloads.apache.org/httpd/CHANGES_2.4.71)
5. [Red Hat — CVE-2026-119618](https://access.redhat.com/security/cve/cve-2026-119618)
6. [Debian Security Tracker — CVE-2026-119618](https://security-tracker.debian.org/tracker/CVE-2026-119618)
7. [icing/mod_h2 — Releases](https://github.com/icing/mod_h2/releases)
8. [Wiz — Critical RCE Vulnerability in Apache HTTP Server: Everything You Need To Know](https://www.wiz.io/blog/cve-2026-119618-rce-apache-http-server-vulnerability)

---
Source page: https://erroneo.us/security/briefs/apache-httpd-mod-http2-rce-cve-2026-119618/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt
