GBHackers

Critical Apache HTTP Server Vulnerability Exploited in the Wild to Gain Remote Code Execution


Attackers are reportedly exploiting CVE-2026-119618, a critical vulnerability in Apache HTTP Server’s HTTP/2 module that can allow unauthenticated remote code execution.

The Cyber Security Agency of Singapore warned on November 17 that exploitation was underway and that a public proof of concept was available. The agency urged administrators to patch immediately but did not identify victims or disclose the scale of the attacks.

Apache fixed the flaw in HTTP Server 2.4.71, released November 11 alongside fixes for two other vulnerabilities. Apache rates CVE-2026-119618 as critical, while Singapore’s advisory cites a high-severity CVSS v3.1 score of 8.1.

Wiz Research had reported no known exploitation when it published its analysis on November 11. The Singapore alert changed that assessment six days after the fix became available.

Apache HTTP Server Vulnerability

The bug resides in assign_headers(), a function in Apache’s mod_http2 module. It is a race condition: threads access a shared resource without proper synchronization, potentially corrupting the heap, where the server stores dynamically allocated data.

Successful exploitation can let a remote attacker run code with the permissions of the Apache process, without logging in. Unlike the earlier HTTP/2 early-reset vulnerability, which involved freeing the same memory twice, this flaw stems from unsafe access to shared memory.

Apache credited Anthropic’s OSS Scanner with reporting the issue on October 26 and Google Cloud Vulnerability Research’s Anthony Weems and Simon Scannell with independently reporting it on November 3. The upstream advisory lists Apache HTTP Server versions 2.4.55 through 2.4.70 and standalone mod_h2 releases 2.0.8 through 2.0.42, inclusive.

As with previous Apache HTTP Server flaws, configuration matters: this vulnerability is exposed when mod_http2 is loaded, and Apache is configured to accept HTTP/2. HTTP/1.1-only servers are not affected.

Wiz found that 64% of the cloud environments it analyzed contained resources running affected versions, while 51% had publicly exposed instances.

Those figures did not account for configuration, so they do not establish how many servers were actually exploitable. Unlike HTTP/2 Rapid Reset, which can overwhelm a service, successful exploitation here can give an attacker control of the web server process and access to data that process can read.

Administrators should prioritize upgrading internet-facing systems to Apache HTTP Server version 2.4.71 or later. Alternatively, they can install a distribution package confirmed by the vendor to contain the fix. Operators who independently build mod_h2 should ensure they move to a patched release that is newer than version 2.0.42.

If immediate patching is not possible, temporarily remove h2 and h2c from the applicable Protocols directives and set the Protocols to http/1.1 as a stopgap measure.

Check the effective configuration for each virtual host, including any Apache backends behind proxies, instead of assuming the protocol settings for the public listener automatically apply to the origin.

After deploying the update, confirm that the running service is using the fixed package across all replicas. If HTTP/2 was temporarily disabled, restore it only after verifying that the fix has been implemented.

Give your SOC the alert context on the latest threats to stop incidents quickly -> Integrate Threat Intel from 16K SOCs:



Source link