The Daily Byte
Breaking
Welcome to The Daily Byte — real stories from across Pakistan.
Saturday, 21 November 2026 · Pakistan

The Daily Byte

Stories from Pakistan that deserve to be heard

CVE-2026-119618: Apache HTTP/2 flaw allows remote code

By The Daily Byte ·15 Nov 2026 ·4 min read
Server racks in a data centre with Apache branding

Apache has released version 2.4.71 of its HTTP Server, fixing a critical flaw in the software's HTTP/2 module that can allow an unauthenticated attacker to run code on the server. The flaw, tracked as CVE-2026-119618, affects every release from 2.4.55 through 2.4.70, and administrators are being urged to update, or switch HTTP/2 off until they can.

Apache rates the flaw critical. Its advisory describes heap corruption in the mod_http2 module's assign_headers() function, caused by concurrent execution using a shared resource without proper synchronisation. Two parts of the server can clash over the same memory while handling HTTP/2 requests, and an attacker can turn that clash into remote code execution on the machine running the web server.

The release, published on 11 November, fixes three vulnerabilities in total. Alongside the critical HTTP/2 flaw, Apache patched an important flaw in mod_md, CVE-2026-106023, which can crash child processes, and a low-severity flaw in mod_vhost_alias, CVE-2026-109163. The HTTP/2 flaw is the one that needs attention first: Red Hat gives it a CVSS base score of 9.8, describing it as unauthenticated remote code execution when HTTP/2 is enabled, with low attack complexity and no privileges or user interaction required.

Reported by two research teams

Apache credits two independent reports for the discovery. Anthropic's OSS Scanner reported the flaw to the Apache security team on 26 October, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it independently on 3 November. The fix landed in the 2.4.71 release on 11 November, the same day the advisory was published.

The standalone mod_h2 module published on GitHub is affected as well, in versions 2.0.8 through 2.0.42. The flaw only affects servers that actually serve HTTP/2 through mod_http2. Apache's default protocol is HTTP/1.1, so a server that does not offer h2 or h2c is not exposed to this particular flaw. That distinction matters for shared and managed hosting, where the protocol in use may not be obvious to the site owner.

Exploit demonstrated, no confirmed attacks yet

Public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled, according to Red Hat's advisory. A public researcher has also posted a test setup reporting memory corruption and Apache child-process crashes on version 2.4.70. At the same time, security company Wiz reported no known exploitation in the wild at the time of its 11 November article, and no confirmed compromise of a live site through this flaw has been reported.

That combination — a demonstrated exploit path and no confirmed attacks so far — is the usual window in which patching matters most. Apache HTTP Server powers a large share of the world's websites, and the affected version range covers more than a year of releases, so many servers will still be running a vulnerable build.

What administrators should do

The fix is to install Apache HTTP Server 2.4.71, or the fixed package from the operating system or hosting vendor, and then restart Apache. Vendor packages may carry a different version number, so administrators should check their supplier's advisory rather than relying on the version number alone.

If a fixed package is not yet available, Apache's HTTP/2 support can be disabled temporarily by removing h2 and h2c from the server configuration, including relevant virtual hosts, and restarting Apache. Servers serving only HTTP/1.1 are not affected.

For WordPress site owners, the important point is that updating WordPress, its plugins or themes will not patch Apache. The flaw sits in the web server software that handles the connection before it reaches PHP or WordPress at all. Site owners on managed or shared hosting should ask their provider whether its Apache servers accept HTTP/2 and whether CVE-2026-119618 has been fixed in the installed package.

Sources: Apache HTTP Server Project security advisory; Wordfence.

Source
Apache HTTP Server Project — https://httpd.apache.org/security/vulnerabilities_24.html