CVE-2026-119618: mod_http2 assign_headers() (shared lock-free allocator between worker and connection threads)
assign_headers() builds per-stream headers on worker threads while connection-level state belongs to the connection thread; both allocate from a shared lock-free allocator without adequate synchronization, so a worker can write into memory the connection thread owns. An unauthenticated attacker controls the race window by opening many concurrent streams on one HTTP/2 connection, and the resulting heap corruption can lead to code execution as the httpd user. Found independently by Anthropic's OSS Scanner and Google Cloud Vulnerability Research.
Executive Summary & Technical Impact
assign_headers() builds per-stream headers on worker threads while connection-level state belongs to the connection thread; both allocate from a shared lock-free allocator without adequate synchronization, so a worker can write into memory the connection thread owns. An unauthenticated attacker controls the race window by opening many concurrent streams on one HTTP/2 connection, and the resulting heap corruption can lead to code execution as the httpd user. Found independently by Anthropic's OSS Scanner and Google Cloud Vulnerability Research.
Tracked under CVE-2026-119618 (CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization)), this vulnerability affects Apache HTTP Server 2.4.55 through 2.4.70 with HTTP/2 enabled; standalone icing/mod_h2 2.0.8 through 2.0.42 (archived, no fix). RHEL 6/7/8 not affected. and carries a severity score of 9.8 (Red Hat; NVD pending) (CRITICAL). Engineering and security operations teams running Apache HTTP Server (httpd) should prioritize upgrading to Apache HTTP Server 2.4.71 (commit 824beab); RHSA-2026:98981 / RHSA-2026:98978 (RHEL 9/10); Debian unstable apache2 2.4.71-1.
Remediation & Patch Guidance
- Upgrade to Apache HTTP Server 2.4.71 or your distribution's fixed package, then restart httpd.
- If patching is delayed, remove h2 and h2c from every Protocols directive (server-wide and per vhost), leaving Protocols http/1.1, and re-verify with curl --http2.
- Rebuild container images, AMIs and auto-scaling templates that bundle httpd; review recent mod_http2 child-process crashes.
Frequently Asked Questions (CVE-2026-119618)
What versions are affected by CVE-2026-119618?
CVE-2026-119618 affects Apache HTTP Server 2.4.55 through 2.4.70 with HTTP/2 enabled; standalone icing/mod_h2 2.0.8 through 2.0.42 (archived, no fix). RHEL 6/7/8 not affected. in Apache HTTP Server (httpd) (mod_http2 assign_headers() (shared lock-free allocator between worker and connection threads)).
How do I patch or remediate CVE-2026-119618?
Upgrade affected deployments to Apache HTTP Server 2.4.71 (commit 824beab); RHSA-2026:98981 / RHSA-2026:98978 (RHEL 9/10); Debian unstable apache2 2.4.71-1 and verify the remediation steps listed above.
What is the CVSS score of CVE-2026-119618?
CVE-2026-119618 is rated CRITICAL with a CVSS score of 9.8 (Red Hat; NVD pending) (vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H; many concurrent HTTP/2 streams on one connection widen the race window).
Apache HTTP Server CVE-2026-119618: A mod_http2 Race Lets One Connection Corrupt the Heap and Run Code
A race condition in mod_http2's assign_headers() lets an unauthenticated attacker corrupt heap memory over a single HTTP/2 connection and potentially execute code. httpd 2.4.55 through 2.4.70 are affected; upgrade to 2.4.71 or turn off h2/h2c.
Read full engineering post-mortem (4 min read) →