Critical Apache HTTP Server RCE Vulnerability Actively Exploited in Attacks

Blog WriterCybersecurity News - Original News Source is cybersecuritynews.com


Apache’s HTTP/2 module, mod_http2, has a critical flaw tracked as CVE-2026-119618 that reportedly allows unauthenticated remote code execution.

Apache released version 2.4.71 on November 11 to fix the flaw, which it rates as critical, while Singapore’s CSA assigns it a high-severity CVSS 3.1 score of 8.1/10.

Singapore’s CSA warned of active exploitation on November 17, 2026, urging administrators to patch immediately. It also noted that a public PoC was available but provided no details about victims or attack scale.

Wiz Research had reported no known exploitation when it published its analysis on November 11. The later alert changes the urgency for administrators who have not yet applied the update.

The bug sits in assign_headers(), a function in the module that handles HTTP/2 traffic. Apache says the function does not properly control how multiple threads access a shared resource.

This creates a race condition, meaning the result depends on which task gets to the resource first. The bug can corrupt the heap, an area of memory the server uses while it runs.

Apache HTTP Server RCE Exploitation

A successful attack can turn that memory corruption into remote code execution (RCE), allowing an attacker to run commands with the web server process’s permissions.

Apache credited Anthropic’s OSS Scanner, which reported the issue on October 26, and Google Cloud researchers Anthony Weems and Simon Scannell, who reported it independently on November 3.

Cybersecurity News previously covered the Apache HTTP Server 2.4.71 patch and a separate Apache HTTP/2 code execution flaw fixed in May. The earlier fix does not protect servers from this vulnerability.

The Apache security advisory lists versions 2.4.55 through 2.4.70 as affected when mod_http2 is enabled. It also lists standalone mod_h2 releases 2.0.8 through 2.0.42 as affected, including 2.0.42 itself.

Servers configured to serve only HTTP/1.1 are not exposed to this flaw. Administrators should check the server’s active protocol settings rather than relying on the version number alone.

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

Those figures do not account for whether HTTP/2 was enabled. They show where teams should check first, not how many environments could be exploited or how many were breached.

Administrators should install Apache HTTP Server 2.4.71 or later, or apply a package their operating system vendor confirms contains the fix.

If an update must wait, temporarily disable HTTP/2 by setting Protocols http/1.1 and checking that individual virtual hosts do not still allow h2 or h2c. After reloading the service, verify that the affected Apache listeners no longer accept HTTP/2.

Start with internet-facing servers, but include internal deployments in the patch plan. For systems that were exposed before the update, keep relevant logs and review them for signs of compromise. Installing the fix closes the vulnerability, but it cannot tell you whether someone exploited it before the upgrade.

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

The post Critical Apache HTTP Server RCE Vulnerability Actively Exploited in Attacks appeared first on Cyber Security News.