← All briefs
critical November 12, 2026

CVE-2026-119618: Unauthenticated RCE in Apache HTTP Server mod_http2 via assign_headers Race Condition

Source report →

On November 11, 2026 the Apache HTTP Server project released version 2.4.71 to fix CVE-2026-119618, a critical concurrency flaw in the HTTP/2 module mod_http2. The flaw is classified as CWE-362 and rated CVSS 3.1 9.8 by Red Hat. It affects Apache HTTP Server 2.4.55 through 2.4.70 and the standalone mod_h2 module in versions 2.0.8 through 2.0.42. Only servers that negotiate HTTP/2 are exposed, meaning the Protocols directive lists h2 or h2c at server level or in any virtual host. Servers limited to HTTP/1.1 are not affected. Anthropic's OSS Scanner reported the flaw on October 26, 2026, and Google Cloud Vulnerability Research reported it independently on November 3, 2026.

The bug sits in the assign_headers() function. The function clones a header table shared by the HTTP/2 stream into the per-request headers, then writes a Content-Length value back into the shared table. The connection thread writes to that same table without a lock while worker threads run assign_headers(), so concurrent requests on one HTTP/2 connection can mutate the table at the same time and corrupt the heap. An attacker who wins the race can turn the corruption into arbitrary command execution as the Apache worker process, with no authentication and no user interaction. The fix writes the value into the per-request table instead of the shared one.

Exploitability depends on the threading model and the memory allocator. Red Hat rates the flaw Important rather than Critical on Red Hat Enterprise Linux 9 and 10, where each HTTP/2 stream gets its own allocator, and states that Red Hat Enterprise Linux 8 and earlier do not contain the vulnerable code. Red Hat also states that public research demonstrated a reliable exploit against a default configuration with mod_http2 enabled, without naming the research. Wiz reported no public exploit and no exploitation in the wild at publication. An independent researcher reproduced the flaw but could not exploit it without disabling default distribution hardening. Neither Apache nor the major distributions enable HTTP/2 by default.

Public detection tooling appeared within hours of disclosure. A scanner published on GitHub on November 11 identifies vulnerable servers in three tiers: it confirms HTTP/2 negotiation, checks the version banner, then sends a deterministic Content-Length oracle request. That request is an HTTP/2 request carrying a Content-Type header, no Content-Length, and END_STREAM on the HEADERS frame, sent to an endpoint that reflects CONTENT_LENGTH such as a CGI script, a PHP page or a proxied backend. Vulnerable versions leave CONTENT_LENGTH unset, while fixed versions report zero. A second scanner repository followed on November 12. Wiz notes that a compromised Apache instance in a cloud workload can be used to reach adjacent microservices and cloud metadata endpoints.

Detections (10)

Enable detections →

Connect your environment for suggestions and queries personalized to your security telemetry.

  • Apache httpd Worker Abnormal Termination
  • Network or Transfer Tool Spawned by Apache httpd
  • Web Server Worker Requesting Cloud Credentials
  • Reconnaissance or Download Command Spawned by PHP Web Worker
  • Fetch From a Bare IP Address URL Spawned by PHP or Apache Worker
  • Network Callback Carrying Host Identity via Shell Command Substitution
  • Cron Job Written by Web Service Account or PHP Web Worker
  • New User Account Created by Web Service Account or PHP Web Worker
  • HTTP/2 Requests Matching the Public CVE-2026-119618 Scanner Oracle