Apache HTTP Server 2.4.71 Fixes Critical mod_http2 Heap Corruption (CVE-2026-119618) — Patch Now

Apache HTTP Server security advisory, Critical, CVE-2026-119618, not in CISA KEV.

Update (13 Nov 2026): Since this post went live, Red Hat has rated the issue Critical with CVSS 3.1 9.8, described it as unauthenticated remote code execution affecting only servers with HTTP/2 enabled, and stated that public research has demonstrated a reliable exploit. Red Hat does not name that research or say the flaw is exploited in the wild. Wiz published exposure figures, Debian, Ubuntu and Red Hat shipped fixed packages, and Red Hat and Wiz document disabling HTTP/2 as a temporary step. The issue is still not in CISA KEV, and upgrading to 2.4.71 remains the fix. Details are below.

The Apache HTTP Server Project released version 2.4.71 on 11 November 2026. Its 2.4 vulnerabilities page lists CVE-2026-119618 under "Fixed in Apache HTTP Server 2.4.71," "Released 2026-11-11," and Apache rates it "(critical)." Apache titles it "mod_http2: heap corruption and RCE in assign_headers" and describes it as: "Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server's mod_http2 in assign_headers() can lead to RCE."

Apache states: "This issue affects Apache HTTP Server: from 2.4.55 through 2.4.70." And: "Affected releases of mod_h2 from GitHub: from 2.0.8 through 2.0.42." The download page lists 2.4.71 as "the latest available version," and the 2.4.71 announcement, dated "November 11, 2026," calls it "recommended over all previous releases." Apache gives no clock time for the release.

Technical Information

CVE-2026-119618, rated critical by Apache. The CVE.org record, published by the Apache CNA, repeats the title and description and lists CWE-362. Apache does not state attacker preconditions. Red Hat's CVE page states that "A remote attacker who can reach the web server could exploit this flaw to execute arbitrary commands on the server without any authentication," and: "Only servers that have HTTP/2 enabled are affected; servers configured to serve only HTTP/1.1 are not vulnerable."

Severity. Apache's page, Eric Covener's oss-security advisory (11 November 2026, 14:19 Asia/Jerusalem UTC+2) and the CVE.org record all give the textual rating "critical," with no CVSS score. NVD's entry, rechecked 13 November 2026, is "Awaiting Analysis" with no metrics. Red Hat assigns CVSS 3.1 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and rates the flaw Critical, but rates Red Hat Enterprise Linux 9 and 10 Important, because their mod_http2 packages "allocate each HTTP/2 stream from a separate allocator, which substantially increases the complexity of exploiting the flaw." This post keeps Apache's "critical" rating and reports Red Hat's score as Red Hat's.

Credits and timeline. Apache credits "Anthropic's OSS Scanner, as vulnerability ANT-2026-MAPKT6MZ" and "Anthony Weems and Simon Scannell of the Google Cloud Vulnerability Research." Its timeline shows reports on 2026-10-26 (Anthropic) and 2026-11-03 (Google), and the fix and 2.4.71 release on 2026-11-11. CHANGES_2.4.71 carries the Anthropic credit only; this post follows the vulnerabilities page.

Other fixes in 2.4.71. The same release fixes CVE-2026-106023, rated "(important)" (mod_md NULL pointer dereference, 2.4.30 through 2.4.70), and CVE-2026-109163, rated "(low)" (mod_vhost_alias, 2.4.69 and 2.4.70).

Related, different issue. CVE-2026-119618 is not CVE-2026-23918, the earlier mod_http2 double-free fixed in 2.4.66 and covered in a separate Rescana post.

Affected Product Versions

From Apache's 2.4 vulnerabilities page:

Component Affected, as Apache states it Fix
Apache HTTP Server from 2.4.55 through 2.4.70 2.4.71, released 2026-11-11
mod_h2 from GitHub from 2.0.8 through 2.0.42 No fixed official mod_h2 release is named yet

At the 13 November 2026 check (09:00 Asia/Jerusalem UTC+2), the newest icing/mod_h2 tag was still v2.0.42. This post does not name a fixed official mod_h2 version.

Distribution packages, rechecked 13 November 2026 at 09:00 Asia/Jerusalem UTC+2:

  • Debian (tracker): fixed in sid (2.4.71-1), bookworm security (2.4.71-1~deb12u1, DLA-4902-1) and trixie security (2.4.71-1~deb13u1, DSA-6620-1), both 12 November 2026. Testing (forky) is still marked vulnerable at 2.4.69-1.
  • Ubuntu (CVE page, priority High; USN-9090-1, 12 November 2026): fixed apache2 packages for 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS, a Ubuntu Pro fix for 20.04 LTS; 18.04, 16.04 and 14.04 LTS not affected. Ubuntu notes that newer module versions were backported, so the upstream version number alone may not show whether an Ubuntu package is fixed.
  • Red Hat (CVE page): fixed mod_http2 packages for Enterprise Linux 9 and 10, including listed EUS and E4S streams, dated 11 November 2026. Enterprise Linux 8 and earlier are not affected. Red Hat Hardened Images (httpd) and JBoss Core Services (jbcs-httpd24-mod_http2) are listed as Affected, with no fixed package listed at the check.

Exploitation Status

Apache's vulnerabilities page, the oss-security advisory, the 2.4.71 announcement, the CVE.org record and the NVD entry do not discuss known attacks, in-the-wild exploitation or proof-of-concept code.

Red Hat's CVE page states: "public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled." It does not name or link that research, and it does not say the issue is being exploited in the wild.

Wiz, in a post published 11 November 2026 at 21:49 Asia/Jerusalem UTC+2, wrote: "As of the time of this blog's publication, no exploit is available and there are no reports of exploitation in the wild." That statement is dated to its publication. The same post reported: "According to Wiz data 64% of cloud environments have resources vulnerable to CVE-2026-119618, and 51% of cloud environments have publicly exposed instances. Note that this does not take configuration into account."

SecurityWeek reported on 12 November 2026 that "A publicly available proof of concept (PoC) on GitHub reports reproducing memory corruption and Apache process crashes, but does not demonstrate remote code execution." This post does not link that proof of concept.

CVE-2026-119618 was not in CISA KEV at the 13 November 2026 check at 09:00 Asia/Jerusalem UTC+2 (catalogVersion 2026.11.10). This post does not claim that the issue is being exploited in the wild.

Workaround and Mitigation

Apache has published no workaround. Its remediation is to upgrade to Apache HTTP Server 2.4.71 from the official download page, or to install a distribution package that contains the fix.

Until then, Red Hat's bulletin RHSB-2026-017 (public date 12 November 2026) and Wiz document a temporary mitigation: remove h2 and h2c from the Protocols directive, leaving Protocols http/1.1, then restart httpd. Red Hat says this "reduces the attack surface until a patched version is deployed." It is an interim step, not a substitute for the upgrade, and not an official Apache workaround.

Indicators of Compromise

Apache has published no indicators of compromise or detection guidance for CVE-2026-119618, and this post does not supply any.

What to Ask Your Vendors Today

If a supplier runs Apache HTTP Server on services that handle your data, ask them in writing. These are questions about the vendor's own posture, not Apache guidance:

  • Whether their internet-facing Apache HTTP Server instances are on 2.4.71 or a vendor package that contains the fix, and which version each was on before.
  • For any instance not yet upgraded, the patch ETA, and whether they have disabled HTTP/2 in the meantime, the temporary step Red Hat and Wiz document.
  • Whether any service uses the standalone mod_h2 module from GitHub (2.0.8 through 2.0.42), and their plan for it.
  • How they will tell you if they find signs of compromise.

If you operate Apache HTTP Server yourself, upgrade to 2.4.71, or your distribution's fixed package, first, then check the same points against your own inventory.

If your team needs help reviewing which suppliers front you with Apache HTTP Server and whether those fleets are on 2.4.71, Talk to an expert.

Sources

Talk to an expert

Talk to Rescana about this advisory — or about how we help TPRM teams keep reviews moving.