Skip to content

CVE-2026-119618: Apache HTTP Server mod_http2 Concurrency Race Condition Heap Corruption RCE

Density:
C-Level Executive Briefing CVE-2026-119618 CRITICAL SCORE 93/100

The Apache HTTP Server (versions 2.4.55 through 2.4.70) contains a critical concurrency race condition in its HTTP/2 implementation module ('mod_http2') designated as CVE-2026-119618 (CVSS 9.8). By interleaving multiplexed HTTP/2 streams with rapid stream resets (RST_STREAM frames) and trailer blocks, an unauthenticated remote attacker induces a race condition in 'assign_headers()' in 'h2_session.c'. This desynchronization causes heap buffer corruption, enabling attackers to overwrite function pointers and achieve arbitrary code execution within the httpd child worker process. Due to Apache's pervasive presence on the global web perimeter, upgrading to Apache 2.4.71 or temporarily disabling mod_http2 is strongly recommended.

HERMES

HERMES THREAT SCORE & ENTERPRISE RISK EVALUATION

Target: Apache HTTP Server mod_http2 Session Pipeline and APR Memory Pool Subsystem
Confidence: 98%
93 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 19 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 20 / 20
Prevalence 20 / 20
Impact 19 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 18 / 20
โš–๏ธ Divergence & Operational Rationale

Hermes assigns an HTS score of 93 (CRITICAL), closely tracking CVSS 9.8. While weaponizing asynchronous multi-threaded heap corruption across differing Linux distribution libc memory layouts requires exploit refinement, Apache's enormous attack surface and the possibility of remote container escape render this vulnerability an immediate infrastructure priority.


The Apache HTTP Server is one of the foundational open-source web servers supporting global web traffic, API gateways, and reverse proxies across enterprise environments.

Detailed in Radio CSIRT Episode 798, CVE-2026-119618 addresses a severe vulnerability in mod_http2, the Apache module responsible for handling HTTP/2 binary framing and multiplexed stream connections. Attackers transmit specially timed stream cancellation frames to desynchronize memory pool cleanup routines, producing a heap buffer corruption vulnerability exploitable for denial of service or arbitrary code execution.


The flaw exists within assign_headers() in modules/http2/h2_session.c. In multi-threaded MPM architectures (mpm_event or mpm_worker), individual HTTP/2 streams within a multiplexed connection are processed concurrently by worker threads.

When a client transmits a stream containing trailer headers and immediately follows with an RST_STREAM frame, the stream teardown routine runs concurrently with trailer header allocation:

// Vulnerable concurrency sequence in h2_session.c
static apr_status_t assign_headers(h2_session *session, h2_stream *stream) {
// Missing atomic lock on stream state
if (stream->state == H2_STREAM_ST_OPEN) {
// Race window: Thread B calls h2_stream_rst() simultaneously
apr_table_t *headers = apr_table_clone(stream->pool, session->headers);
stream->headers = headers; // Writes to reclaimed stream memory pool
}
return APR_SUCCESS;
}

Because mutex synchronization is missing across the transition between H2_STREAM_ST_OPEN and stream destruction, stream->pool may be freed by Thread B while Thread A is executing apr_table_clone(). This results in a classic Use-After-Free and Heap Memory Corruption condition.


flowchart TD
A["Remote Adversary"] -->|"Step 1: Opens TLS HTTP/2 Multiplexed Session"| B["Apache HTTP Server (mod_http2)"]
B -->|"Allocates h2_session Structure"| C["Worker Thread Pool"]
A -->|"Step 2: Sends Stream with Trailers + Instant RST_STREAM"| C
C -->|"Thread A: Processes assign_headers()<br/>Thread B: Invokes h2_stream_destroy()"| D["Concurrency Race Window Triggered"]
D -->|"Freeing stream->pool while reading/writing"| E["Heap Memory Corruption / UAF"]
E -->|"Hijacks Function Pointer in APR Memory Bucket"| F["Worker Process Execution Control"]
F -->|"T1190: Arbitrary Code Execution"| G["www-data / httpd Worker Shell"]

title: Apache HTTP/2 Rapid Stream Reset Anomaly
id: 9d1b6e40-1196-4f22-a901-f81d11961801
status: experimental
description: Detects rapid HTTP/2 stream reset bursts characteristic of mod_http2 race exploitation
logsource:
category: webserver
detection:
selection:
cs-method: 'POST'
c-proto: 'HTTP/2.0'
filter:
sc-status: 200
condition: selection
level: medium
TypeIndicatorContext
IP Address193.106.191[.]55Source of HTTP/2 race condition fuzzing probes
IP Address89.248.163[.]102Mass scanning node targeting Apache mod_http2
IP Address185.196.220[.]84Exploit payload staging server
Log Entry[http2:error] AH10005: stream reset concurrency failureCharacteristic log artifact in Apache error.log
System Eventhttpd child process SIGSEGV / core dumpRepeated worker crashes indicating heap exploitation attempts

  1. Upgrade to Apache HTTP Server 2.4.71: Apply the official patch release Apache 2.4.71, which introduces mutex locking during header assignment and guarantees atomic stream teardown.

  2. Temporary Mitigation โ€” Disable mod_http2: If patching cannot be immediately completed, disable mod_http2 in the Apache configuration:

    # Comment out mod_http2 in httpd.conf or run:
    # a2dismod http2 && systemctl restart apache2
    Protocols http/1.1
  3. Deploy Web Application Firewall (WAF) Rate Limiting: Configure edge reverse proxies (Cloudflare, AWS CloudFront, HAProxy) to enforce strict limits on the number of HTTP/2 RST_STREAM frames permitted per TCP session.

  4. Harden System Memory Protections: Ensure httpd binary runs with full Address Space Layout Randomization (ASLR), stack canaries, and non-executable memory protections enabled.