~/f4n6 $ grep -r "Apache patches critical HTTP/2 RCE CVE-2026-119618 found by Anthropic" ./investigations/ --include="*.md"

Apache patches critical HTTP/2 RCE CVE-2026-119618 found by Anthropic

Jeff Davies 12 Nov 2026 4 min read

1. Executive summary

Apache has released version 2.4.71 of the Apache HTTP Server to fix CVE-2026-119618, a race condition in the mod_http2 module that could let an unauthenticated attacker execute code on servers with HTTP/2 enabled. The flaw affects versions 2.4.55 through 2.4.70. SecurityWeek reports the bug was found by Anthropic and Google. NVD has not scored CVE-2026-119618, so no verified CVSS severity exists; the "critical" label in the source headline is the publisher's wording, not a scored rating. The CVE is not in CISA KEV and EPSS records 0%, which indicates no observed exploitation to date. For EMEA financial services the exposure is concentrated in internet-facing web tiers that terminate HTTP/2 directly on Apache, and the fix is a single version bump.

2. Regulatory framing

No specific DORA/NIS2 article is directly engaged by this item.

3. Technical analysis & attack chain

CVE-2026-119618 is a race condition (CWE-362) in mod_http2, the Apache HTTP Server module that handles the HTTP/2 protocol. The source describes it as a race condition that could let unauthenticated attackers execute code on servers with HTTP/2 enabled. The affected range is 2.4.55 through 2.4.70; 2.4.71, released 2026-11-11, is the fixed version. Only servers with HTTP/2 enabled are affected, per Red Hat, which ships the server as part of Red Hat Enterprise Linux.

The confirmed attack chain, as far as public reporting supports it:

  1. The target runs Apache HTTP Server 2.4.55 through 2.4.70 with mod_http2 loaded and HTTP/2 enabled.
  2. An unauthenticated remote attacker who can reach the HTTP/2 listener triggers the race condition.
  3. The race condition can lead to code execution on the server.

The sources do not state the precise interleaving the race requires, the request sequence that wins it, whether exploitation is reliable or probabilistic, or what privileges the executed code runs at. They do not name a proof-of-concept, an in-the-wild exploitation attempt, or a victim. CISA KEV does not list the CVE and EPSS records 0%, so there is no public evidence of exploitation. The "found by Anthropic, Google" attribution for discovery appears in the SecurityWeek headline and is single-sourced; treat the finder credit as reported, not confirmed.

The mechanism is a race condition, which means the window depends on concurrent request handling in mod_http2. That has two practical consequences for defenders. First, a server that does not have HTTP/2 enabled is not exposed, so the first triage question is whether mod_http2 is loaded and the protocol is offered. Second, because the flaw is in request handling rather than application code, WAF rules written against application payloads will not reliably catch it; the fix is the version bump.

A related ANSSI advisory (CERTFR-2026-AVI-1248, dated 02 October 2026) describes multiple vulnerabilities in Apache HTTP Server, some allowing remote arbitrary code execution, remote denial of service and a confidentiality impact. That advisory predates this CVE's disclosure and is a separate Apache HTTP Server bulletin; it is not a source for CVE-2026-119618's mechanism and its details are not carried into this advisory.

4. Mitigation & containment

P1 within 24h

  • Inventory every Apache HTTP Server instance and record its version. Any instance at 2.4.55 through 2.4.70 with mod_http2 loaded and HTTP/2 enabled is in scope.
  • Upgrade in-scope instances to 2.4.71. This is the fixed release named in public reporting. Where the server is the Red Hat Enterprise Linux package, take the vendor's updated package rather than building from source.
  • Where 2.4.71 cannot be deployed immediately, disable HTTP/2 on the affected virtual hosts so mod_http2 does not serve requests. The sources state that only servers with HTTP/2 enabled are affected; they do not name a specific configuration directive, so confirm the correct directive for your build against the Apache documentation before changing production config.

P2 within 72h

  • Confirm the upgrade took effect by checking the reported server version on each listener after restart, not just the package version on disk.
  • Review Apache access and error logs on any instance that was internet-facing at an affected version for anomalies around HTTP/2 request handling. The sources give no specific log signature, so this is a hunt for unexplained crashes, restarts or process behaviour on the HTTP/2 listener rather than a signature match.

P3 within 7 days

  • Add Apache HTTP Server version to the standard asset inventory feed so future mod_http2 advisories can be matched without a manual sweep.
  • Where HTTP/2 is not a business requirement on internal or partner-facing tiers, leave it disabled to reduce the exposed surface.

No fixed release other than 2.4.71 is named in public reporting for this CVE. No vendor workaround beyond disabling HTTP/2 is named.

5. Indicators of compromise

No indicators of compromise available in the source material.

6. Detection

Insufficient indicators to author detection rules.

CVE assessment

1 referenced CVE

CVE CVSS Exploited EPSS Summary
CVE-2026-119618 — — 0% Concurrent Execution using Shared Resource with Improper Synchronization vulnerability in Apache HTTP Server's mod_http2 in ass…

7. Sources

  • 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/, 2026-11-12
  • The Hacker News, Critical Apache HTTP/2 Flaw Could Let Unauthenticated Attackers Execute Code Remotely, https://thehackernews.com/2026/11/critical-apache-http2-flaw-could-let.html
  • ANSSI France CERT, Multiples vulnérabilités dans Apache HTTP Server, https://www.cert.ssi.gouv.fr/avis/CERTFR-2026-AVI-1248/, 2026-10-02 (separate Apache HTTP Server bulletin, not a source for CVE-2026-119618)

8. Adverse Trace position

Adverse Trace assesses CVE-2026-119618 as a race condition in mod_http2 with no verified CVSS score from NVD, not listed in CISA KEV, and an EPSS of 0%, so there is no public evidence of exploitation and the client risk rests on exposure rather than observed attacks. The finder credit to Anthropic and Google is single-sourced to SecurityWeek and should be treated as reported rather than confirmed. The client impact for EMEA financial services is bounded: any internet-facing Apache HTTP Server at 2.4.55 through 2.4.70 with HTTP/2 enabled should be upgraded to 2.4.71 or have HTTP/2 disabled, and instances without HTTP/2 are not exposed. We will monitor for a CISA KEV addition, an NVD score, and any proof-of-concept or in-the-wild reporting, and will reissue this advisory if exploitation is confirmed.


Read the original source →

Published via PulseTrace — Adverse Trace threat intelligence.

Post this to LinkedIn
Formatting is converted automatically — headings, bullets, a link back & hashtags. Paste straight in.
J
Jeff Davies