CVE-2026-119618Nov 16, 2026

CVE-2026-119618

A critical severity CVE in the mod_http2 Apache module was announced on November 11th, 2026. The following article summarizes currently known data about this vulnerability, possible impact, available detections, and suggested remediations.

5 min read

Introduction

A critical severity CVE in the mod_http2 Apache module was announced on November 11th, 2026. The following article summarizes currently known data about this vulnerability, possible impact, available detections, and suggested remediations.

CVE-2026-119618

CVE-2026-119618 is a critical (CVSS v3: 9.8) in the mod_http2 module in the Apache webserver. It is a Concurrent Execution using Shared Resource with Improper Synchronization vulnerability, which can lead to remote code execution (RCE). It affects the mod_http2 module in Apache versions from 2.4.55 through 2.4.70, and the mod_h2 module published on GitHub form 2.0.8 through 2.0.42.

The vulnerability was independently discovered and reported by two groups; Anthropic (using the OSS scanner) reported the vulnerability to the Apache project on 2026-10-26, and Anthony Weems and Simon Scannell of the Google Cloud Vulnerability Research team reported it on 2026-11-03, 8 days later.

Fixes were completed in version 2.4.x on 2026-11-11 and released as version 2.4.71 the same day.

The mod_h2 project, however, was archived by the repository owner on June 9th, 2026, and no patches have been made available.

Vulnerability Context

Apache is a widely used webserver on the internet, accounting by some estimates for between 13-21% of active internet sites. 21% of active internet sites.1

This vulnerability, however, may not be as widespread as overall Apache use, since it depends on the mod_http2 or mod_h2 modules being configured and activated, and this is not default on most stock installations of Apache. Nevertheless, there will be a significant number of affected servers, and immediate investigation and remediation activities are warranted.

How the Vulnerability Works

This vulnerability is essentially a race condition between two threads that share data which do not properly lock a function called ‘assign_headers()’, allowing the possibility of heap memory corruption, up to and including the possibility of remote code execution.

HTTP/2 is designed to allow multiple requests over a single connection. The mod_http2 module handles this using multiple threads. This vulnerability lies in the handling of concurrent requests; one thread can write into the memory of another thread through a shared, lock-free allocator. This vulnerability can be triggered without any authentication by any client that can connect to the server.

Observed Exploit Behavior

At the time of this publication, we have observed no major exploit activity. However, Red Hat has said that public research has demonstrated a reliable exploit against a default configuration.2

From a network protocol inspection perspective, the general pattern of exploit activity would be a request with the “Content-Type” header set but no “Content-Length” header set. However, this may lead to false positives, as these signals can occur in legitimate traffic as well. More sophisticated network detections would include identifying requests at specific sizes related to triggering the exploit. On the server-side, likely exploit attempt behaviour will likely be unexpected child process termination, segmentation faults, worker resets, HTTP/2 connection resets, and similar side effects of memory corruption.

Conclusion

Coming on the heels of PHP2Shell and several other critical vulnerabilities in widely used software, along with discovery credit going to the Anthropic OSS scanner, this flaw further demonstrates the challenges faced by enterprise security teams. While no current exploitation has been observed, that is likely to change very quickly.

Users of Apache should immediately audit their configurations for the use of the mod_http2 module, and disable it at a minimum, while preparing to update to the fixed version of 2.4.71. A quick fix can be enabled by setting the Protocols field in the Apache configuration to remove the “h2” and “h2c” parameters if present and reloading the webserver; this effectively forces clients to not use HTTP/2. This should be considered only a short-term workaround, and priority should be given to upgrading to an unaffected version, as forcing the HTTP/1.1 protocol may expose the server to request smuggling vulnerabilities, if the previous configuration was HTTP/2 only.

Recommendations

  1. Upgrade Apache as and when operationally possible.
    Prioritize upgrading all internet-facing Apache deployments which use mod_http2 to fixed releases
  2. Deploy Behavioural Detections
    Organizations can leverage monitoring tools to detect unusual behaviours of Apache processes and use advanced web application firewalls to detect possible attempts at exploitation. For instance, platforms like F5 WAF for Distributed Cloud, or F5 WAF for NGINX can be used to identify HTTP/2 requests matching the above-mentioned signals, block high-frequency requests that may indicated attempted exploitation, and even block such traffic from reaching vulnerable Apache servers until updates can be deployed.


Share
Tags:CVE-2026-119618,Espionage,Sensor Intel Series,Vulnerability

About the author

Malcolm Heath

Malcolm Heath

Principal Cybersecurity Threat Researcher | F5

Malcolm Heath is the Principal Threat Researcher with F5 Labs. His career has included incident response, program management, penetration testing, code auditing, vulnerability research, and exploit development at companies both very large and very small. Prior to joining F5 Labs, he was a Senior Security Engineer with the F5 SIRT.

More research by Malcolm Heath