Vulnerability DatabaseCVE-2026-119618

CVE-2026-119618: 
Apache HTTP Server vulnerability analysis and mitigation

Overview

CVE-2026-119618 is a race condition (Concurrent Execution using Shared Resource with Improper Synchronization) in Apache HTTP Server's mod_http2 module within the assign_headers() function that can lead to remote code execution (RCE). It affects Apache HTTP Server versions 2.4.55 through 2.4.70, and standalone mod_h2 GitHub releases from 2.0.8 through 2.0.42. The vulnerability was disclosed on November 11, 2026, with patches released the same day. It carries a CVSS v3.1 base score of 8.1 (High), reflecting network-based exploitation with no authentication or user interaction required, though attack complexity is rated High (Apache Advisory, GitHub Advisory).

Technical details

The root cause is a race condition (CWE-362) combined with improper input validation (CWE-20) in the assign_headers() function of mod_http2. When a client sends a bodyless POST request with a Content-Type header but no Content-Length header and the END_STREAM flag set on the HEADERS frame, the function synthesizes a Content-Length: 0 value and writes it into a shared per-stream header table. This write races with concurrent reads by a different worker thread, causing heap corruption. The attack surface requires HTTP/2 to be enabled (h2 or h2c in the Protocols directive). Exploitation involves opening many parallel HTTP/2 connections and flooding streams with crafted header-heavy requests (typically 78+ filler headers to saturate the HPACK header table) to maximize the probability of hitting the race window. Public PoC tools confirm the heap corruption is reliably triggerable; at least one repository (studiogangster/CVE-2026-119618) claims to demonstrate actual RCE via a CGI handler path (Apache Advisory, GitHub Advisory).

Impact

Successful exploitation can result in full compromise of the affected Apache HTTP Server instance, with high impact to confidentiality, integrity, and availability. An unauthenticated remote attacker can execute arbitrary commands with the privileges of the web server process (typically www-data or apache), enabling data exfiltration, web shell deployment, lateral movement within the hosting environment, and denial of service via worker process crashes. Internet-facing servers with HTTP/2 enabled are directly exposed, and the vulnerability is particularly significant given Apache HTTP Server's widespread deployment across web hosting infrastructure (Apache Advisory, GitHub Advisory).

Exploitability

Multiple public proof-of-concept tools appeared on GitHub within 24 hours of disclosure, including scanners, crash PoCs, and at least one claimed RCE exploit (studiogangster/CVE-2026-119618) that targets a CGI handler path. Active in-the-wild exploitation has been reported by multiple sources including CyberSecurityNews and GBHackers, and Singapore's CSA issued an urgent patching advisory (CSA Alert, CyberSecurityNews). The EPSS score is approximately 0.40% (per Feedly data), though exploitation has been confirmed in the wild. The vulnerability is not yet listed in the CISA KEV catalog based on available data. Notably, the vulnerability was discovered with involvement from Anthropic and Google researchers (SecurityWeek).

Exploitation steps

  1. Reconnaissance: Identify internet-facing Apache HTTP Server instances running versions 2.4.55–2.4.70 using tools like Shodan, Censys, or Nmap NSE scripts. Confirm HTTP/2 support via TLS ALPN negotiation (h2) or cleartext upgrade (h2c) by sending an HTTP/2 preface and checking for a SETTINGS frame response.
  2. Version fingerprinting: Send a HEAD request and parse the Server response header for the Apache version string matching the affected range (2.4.55–2.4.70). Passive scanners like foxcornlab/apache-httpd-scanner automate this step.
  3. Functional probe: Send a single bodyless POST request with Content-Type: application/x-www-form-urlencoded, no Content-Length header, and END_STREAM set on the HEADERS frame. Check server access logs or response behavior for evidence that assign_headers() synthesizes Content-Length: 0, confirming the vulnerable code path is reachable.
  4. Concurrent burst construction: Build trigger HEADERS frames: POST method, Content-Type present, no Content-Length, END_STREAM set, and approximately 78 filler x-pad-NNN headers to fill the HPACK header table to capacity. Interleave with benign GET flood streams to saturate the worker pool.
  5. Race trigger: Open N parallel HTTP/2 connections (e.g., 8–16) and simultaneously flush batches of trigger and flood streams across all connections. Optionally send RST_STREAM (CANCEL) frames immediately after stream creation to race server-side stream cleanup. Repeat across multiple waves to maximize concurrency.
  6. Corruption detection: Monitor for RST_STREAM frames with non-zero error codes, connection closures (EOF/GOAWAY), or 5xx responses disproportionate to baseline traffic — these indicate heap corruption in the worker process.
  7. RCE (if CGI/handler available): If the target runs a CGI handler (e.g., mod_cgid, PHP, SSI), pass a command in the X-Cmd header or request body via the trigger stream. Capture command output from the X-Cmd-Out response header or response body to confirm arbitrary code execution as the web server process user (GitHub Advisory, Apache Advisory).

Indicators of compromise

  • Network: Unusually high volumes of concurrent HTTP/2 connections from a single source IP; streams with POST method, Content-Type header, no Content-Length, and END_STREAM set on HEADERS frames; RST_STREAM frames with error code 0x8 (CANCEL) sent immediately after stream creation; GOAWAY frames with non-zero error codes from the server; outbound connections from the Apache process to unknown external IPs (potential reverse shell).
  • Logs: Apache access_log entries showing repeated bodyless POST requests to arbitrary paths with Content-Type but no Content-Length; error_log entries containing sanitizer markers (ASAN/TSAN/UBSAN) referencing assign_headers or heap corruption; abnormal child process crash/restart messages ([notice] child pid XXXX exit signal Segmentation fault).
  • Process: Unexpected child processes spawned by the Apache worker process (e.g., /bin/sh, bash, curl, wget, python); Apache worker processes consuming abnormally high memory or crashing repeatedly; CGI processes executing unexpected system commands.
  • File System: New web shells or scripts in the document root or CGI directories; unexpected cron jobs or systemd timers created by the www-data or apache user; modified Apache configuration files enabling additional CGI handlers or modules.
  • Behavioral: Server returning intermittent 5xx errors under moderate load; HTTP/2 connections being terminated unexpectedly; mod_status showing abnormally high numbers of active workers or connection resets (Apache Advisory, GitHub Advisory).

Mitigation and workarounds

Primary remediation: Upgrade Apache HTTP Server to version 2.4.71 or later, which contains the fix (commit 824beab9b9424d6cfb29595248fdbf6c3dddeab1). For standalone mod_h2 from GitHub, upgrade to version 2.0.43 or later. Distribution-specific patches are available from Red Hat (RHSA-2026:98982, RHSA-2026:98968, RHSA-2026:100550), Ubuntu (USN-9090-1), SUSE (SUSE-SU-2026:5235-1), Amazon Linux (ALAS2023-2026-3458, ALAS2-2026-4114), and others (Apache Advisory, GitHub Advisory).

Workaround (if immediate patching is not possible): Disable HTTP/2 by removing h2 and h2c from the Protocols directive in Apache configuration:

Protocols http/1.1

This eliminates the attack surface entirely. Verify the change is effective by confirming the server no longer negotiates HTTP/2 via ALPN. Additionally, implement network-level controls (WAF rules, rate limiting on concurrent HTTP/2 connections) to reduce exposure while patches are deployed (cPanel Advisory).

Community reactions

The vulnerability generated significant community attention immediately after disclosure. SecurityWeek reported that the flaw was discovered with involvement from Anthropic and Google researchers, which drew notable interest given the AI-assisted discovery angle (SecurityWeek). Security researcher GossiTheDog (@GossiTheDog on Mastodon) commented on the vulnerability shortly after disclosure. Wordfence published a PSA specifically for WordPress site owners given Apache's prevalence in WordPress hosting environments. Imperva, Wiz, Praetorian, Horizon3.ai, Sysdig, Orca Security, and F5 Labs all published technical analyses and customer advisories within 48 hours. There was notable debate in the community (covered by dugganusa.com) about the severity discrepancy between Red Hat's assessment and Wiz's analysis. The vulnerability trended heavily on Hacker News and across security-focused Mastodon instances, with Singapore's CSA issuing an urgent advisory urging immediate patching after active exploitation was confirmed (CSA Alert, SecurityWeek).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

apache2: 2.4.71-1~deb12u1

Fixed

sid

apache2: 2.4.71-1

Fixed

trixie

apache2: 2.4.71-1~deb13u1

Fixed

Ubuntu

Fixed

bionic (esm-infra)

apache2

Not Affected

devel

apache2: 2.4.68-1ubuntu8

Affected

focal (esm-infra)

apache2: 2.4.41-4ubuntu3.23+esm11

Fixed

jammy

apache2: 2.4.52-1ubuntu4.27

Fixed

noble

apache2: 2.4.58-1ubuntu8.19

Fixed

resolute

apache2: 2.4.66-2ubuntu2.8

Fixed

trusty (esm-infra-legacy)

apache2

Not Affected

xenial (esm-infra-legacy)

apache2

Not Affected

RHEL / CentOS

Fixed

RHEL 8

Not Affected

RHEL 9

:appstream:mod_http2-0:2.0.26-2.el9_4.4.src

Fixed

RHEL 10

mod_http2-0:2.0.29-2.el10_0.3.src

Fixed

Alpine

Fixed

edge

apache2: 2.4.71-r0

Fixed

v3.21

apache2: 2.4.71-r0

Fixed

v3.22

apache2: 2.4.71-r0

Fixed

v3.23

apache2: 2.4.71-r0

Fixed

Source: This report was generated using AI

Related Apache HTTP Server vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-93546HIGH8.8
  • Apache HTTP Server logoApache HTTP Server
  • mod_proxy_html-debuginfo
NoYesOct 01, 2026
CVE-2026-119618HIGH8.1
  • Apache HTTP Server logoApache HTTP Server
  • apache2-worker
NoYesNov 11, 2026
CVE-2026-106023HIGH7.5
  • Apache HTTP Server logoApache HTTP Server
  • apache2-worker
NoYesNov 11, 2026
CVE-2026-109163MEDIUM5.9
  • Apache HTTP Server logoApache HTTP Server
  • mod_ssl-debuginfo
NoYesNov 11, 2026
CVE-2026-79768MEDIUM5.3
  • Apache HTTP Server logoApache HTTP Server
  • httpd:2.4::httpd-tools
NoYesOct 01, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management