Connect with us

NEWS

The Apache HTTP/2 Bug Hits Servers Outside Normal Inventories

CVE-2026-119618 is unauthenticated RCE in Apache’s HTTP/2 module, and the exposed copies are vhosts, RHEL’s separate RPM, archived GitHub builds, and appliances.

Published

on

Apache HTTP Server 2.4.71, released November 11, 2026, patches CVE-2026-119618, a race in the HTTP/2 module that can let an attacker with no login run code. The flaw lives in assign_headers() inside mod_http2 and hits 2.4.55 through 2.4.70 only when HTTP/2 is on.

Anthropic’s OSS Scanner filed it on October 26. Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research filed the same hole on November 3. The copies that still get hurt are the ones whose Apache never shows up as Apache.

A Race in Header Handling Can Run Code

Apache rates the bug critical. It is a CWE-362 race: concurrent execution using a shared resource without proper locking in assign_headers(). The HTTP/2 module hands many streams on one connection to its own worker threads, and a worker can write into memory that belongs to the connection thread through a shared allocator. That corrupts the heap. From there, Apache says, the path can end in remote code execution in the httpd process.

Apache’s 2.4.71 vulnerability list names two finders and a 16-day clock from first report to a public fix. Standalone GitHub builds of the same module, shipped as mod_h2, are in range from 2.0.8 through 2.0.42.

FROM FIRST REPORT TO 2.4.71

  1. October 26, 2026: Anthropic’s OSS Scanner reports the race as ANT-2026-MAPKT6MZ.
  2. November 3, 2026: Anthony Weems and Simon Scannell independently report the same flaw, 8 days after the first filing.
  3. November 6, 2026: Apache HTTP Server 2.4.70 ships, still carrying the bug.
  4. November 11, 2026: Commit 824beab lands and version 2.4.71 is released, 16 days after the first report and 5 days after 2.4.70.
  5. November 12, 2026: Ubuntu and Debian ship fixed packages, and public labs that crash workers appear on GitHub.

A host that moved to 2.4.70 after November 6 is still on the affected list. The upgrade that closed this hole is 2.4.71, not the release from five days earlier.

HTTP/2 Stays Dark Until You Turn It On

The module has been in the 2.4 line since 2.4.17, and it does not speak HTTP/2 because it is loaded. Apache’s own docs say you must enable HTTP/2 via Protocols. The tokens are h2 for HTTP/2 over TLS and h2c for HTTP/2 over plain TCP, and the line can sit in the main server config or in a single virtual host.

Red Hat’s HTTP/2 RCE bulletin is blunt about the gate: servers that serve HTTP/1.1 only are not vulnerable. On Red Hat Enterprise Linux 9 and 10 the module is not even inside the httpd RPM. It ships as a separate mod_http2 package, so a patched httpd binary with an old module still leaves the hole open.

WHAT HAS TO BE TRUE TO BE HIT

  • Module loaded: mod_http2 is loaded in the running server.
  • Protocols line: A server-wide or virtual-host Protocols directive includes h2 or h2c.
  • Network path: An attacker can send HTTP/2 requests to that listener, with no login and no user click.

A clean main config is not a clean server. h2 on one vhost is enough, and a server-wide http/1.1 line does not override a vhost that sets h2. The check is every Protocols line that httpd actually loads, including files a hosting panel wrote.

Who This Bug Reaches

Anyone running stock Apache 2.4.55 through 2.4.70 with h2 or h2c on is in range, and that is the group every advisory names first. The group that lags is different. It is the copy of httpd that a fleet grep never sees, the module a distro split out of the httpd package, and the GitHub build whose maintainers already locked the repo.

On RHEL 9 and 10, the fix is not “install httpd 2.4.71.” It is the rebuilt mod_http2 RPM, RHSA-2026:98981 on RHEL 9 (mod_http2-2.0.26-7.el9_9.1) and RHSA-2026:98978 on RHEL 10 (mod_http2-2.0.29-5.el10_3.1), both dated November 11. RHEL 8 and RHEL 7 are not affected. JBoss Core Services 1 is. An admin who only bumps the httpd package and leaves the old module in memory has not closed the hole.

GitHub’s standalone mod_h2 is worse. Apache lists 2.0.8 through 2.0.42 as affected, 2.0.42 is still the last tagged release, and the project was archived in June 2026. There is no patched standalone tarball. The working path is to stop loading that extra module and use the mod_http2 that ships inside httpd 2.4.71.

Vendor appliances are the copy that never appears in an Apache inventory. Bundled httpd inside a product image does not advertise itself as a web server you patch with apt or dnf. Asking those vendors whether they compiled mod_http2 and whether Protocols includes h2 covers the part a fleet-wide grep cannot reach.

Wiz’s cloud scan, published November 11 by Merav Bar, is easy to misread as a blast radius. It is a version inventory.

WIZ CLOUD COUNTS, NOVEMBER 11

  • Version hits: 64% of cloud environments had resources on an affected Apache version.
  • Public reach: 51% of those environments had an instance on the public internet.
  • Config caveat: The tally does not take HTTP/2 settings into account.
  • Wild use: Wiz recorded no public exploit and no in-the-wild attacks that day.

Those 64% of cloud environments still have to be checked for h2 and h2c. FOFA’s index lists more than 217 million Apache HTTP Server banners from the past year, which is a count of banners, not of HTTP/2, and not of this bug.

Red Hat Scores 9.8 on Unnamed Research

Red Hat Product Security scored the flaw 9.8 on CVSS v3 and called the impact critical. CVE.org scored the same record 8.1 and set attack complexity to High, the usual mark for a race. The gap is the unnamed work Red Hat says already exists.

It allows unauthenticated remote code execution, and public research has demonstrated a reliable exploit against a default-configured server with the mod_http2 module enabled.

Red Hat Product Security, CVE-2026-119618 statement

Red Hat does not name that research, the author, or a link. “Default-configured” in that sentence means a default that has mod_http2 enabled, not that every Apache install turns HTTP/2 on. Wiz, later on November 11, said no exploit was available and that no exploitation in the wild had been reported. Public GitHub labs that appeared November 12 reproduce memory corruption and worker crashes. They do not show a finished remote-code path.

WHERE EXPERTS DISAGREE

  • Red Hat Product Security: CVSS 9.8, low complexity, and a reliable exploit against a default with mod_http2 on, research unnamed.
  • Wiz, November 11: No public exploit, no in-the-wild use, EPSS not in play in its write-up, patch anyway because the vector is network and unauthenticated.
  • CVE.org scoring: 8.1 with High attack complexity, treating the race as harder to land than Red Hat’s 9.8 implies.

watchTowr, investigating the same day the advisory landed, treated the hole as config-bound rather than universal.

It appears to be configuration-specific, with only hosts with h2 enabled in Protocols being exposed. Patch now or drop h2 until you can.

watchTowr, November 11, 2026

Feeds that stamped “public exploit out” on November 13 were describing those crash labs, or Red Hat’s unnamed research, as if they were the same object. They are not. A crash in a sanitizer lab is not a kit that takes over a process, and an unnamed reliable exploit is not a file you can fetch.

Version 2.4.70 Still Carries the Hole

Upstream users move to 2.4.71. Distro users move to the package their vendor numbered, which is often not 2.4.71 on the label. Ubuntu backported the fix into older apache2 builds. RHEL rebuilt the separate module. Debian did ship 2.4.71 in the security archive.

FIXED PACKAGES BY PLATFORM

Platform Advisory Fixed package Note
Apache upstream 2.4.71, November 11 httpd 2.4.71 Also fixes two other CVEs
RHEL 10 RHSA-2026:98978 mod_http2-2.0.29-5.el10_3.1 Separate RPM, not the httpd NVR
RHEL 9 RHSA-2026:98981 mod_http2-2.0.26-7.el9_9.1 Separate RPM, not the httpd NVR
RHEL 8 and 7 Not affected – Vulnerable code not present
Ubuntu 24.04 LTS USN-9090-1, November 12 apache2 2.4.58-1ubuntu8.19 Backport, label is not 2.4.71
Ubuntu 22.04 LTS USN-9090-1, November 12 apache2 2.4.52-1ubuntu4.27 Backport, label is not 2.4.71
Debian 13 DSA-6620-1 apache2 2.4.71-1~deb13u1 trixie-security
Debian 12 DLA-4902-1 apache2 2.4.71-1~deb12u1 bookworm-security
GitHub mod_h2 None None; 2.0.42 is last Repo archived June 2026

Ubuntu’s apache2 package status also lists 26.04 (2.4.66-2ubuntu2.8) and 26.10 (2.4.68-1ubuntu6.2) as fixed in the same USN. Ubuntu 20.04 has a fix only through Ubuntu Pro. 18.04, 16.04, and 14.04 are not affected. Reading the Apache version string alone on Ubuntu 22.04 or 24.04 will look unpatched after a good update, because the NVR never becomes 2.4.71.

Two More Fixes Travel With 2.4.71

The same tarball closes two other bugs that have nothing to do with HTTP/2. Teams that only grep for CVE-2026-119618 will miss why 2.4.69 and 2.4.70 still need the drop even on hosts that never enabled h2.

THE OTHER TWO CVES IN 2.4.71

CVE Apache rating Component Affected builds
CVE-2026-119618 Critical mod_http2 assign_headers() 2.4.55 through 2.4.70; mod_h2 2.0.8 through 2.0.42
CVE-2026-106023 Important mod_md NULL pointer crash 2.4.30 through 2.4.70
CVE-2026-109163 Low mod_vhost_alias 1-byte stack overwrite 2.4.69 and 2.4.70

CVE-2026-106023 can crash a child while mod_md handles a request, which is the Let’s Encrypt automation module that has been in the tree since 2.4.30. CVE-2026-109163 is a leftover after CVE-2026-63292 and only exists in 2.4.69 and 2.4.70. Hosts that skip 2.4.71 because they never turned on HTTP/2 still pick up those two if they run those modules.

Turn Off h2 and Prove It

Apache’s advisory does not offer a workaround. Red Hat and Wiz both do: take h2 and h2c off every Protocols line, leave Protocols http/1.1, and restart httpd so the old module is not still in memory. Browsers and API clients fall back to HTTP/1.1 without a client change. Files then go out one after another instead of multiplexed, and headers go out as uncompressed text.

The change has to hit virtual hosts, not only the global file. Then prove the listener from outside, not from the config you think you saved.

Red Hat’s client check is curl -kI –http2 against the site. HTTP/2 200 means the protocol is still on. HTTP/1.1 200 means it is off. On the server, grep -r Protocols across the main config and every conf.d and vhost file, ignore commented lines, and confirm no live h2 or h2c remains. apachectl -M | grep http2 only tells you the module is loaded. It does not tell you whether Protocols turned it on.

Reload is not optional. An edited file with the old module still mapped in a running process is the same server you had before the edit. GitHub mod_h2 users get the same Protocols cut, because there is no patched 2.0.x for them to install.

The upstream fix is 2.4.71. The RHEL fix is the mod_http2 RPM. The Ubuntu fix is a backport whose version string still looks old. The GitHub module has no fix, and appliance vendors still have to say whether they compiled h2 in. Those are different jobs, and they are the ones this advisory actually assigns.

Frequently Asked Questions

Which Apache Versions Does CVE-2026-119618 Affect?

Apache HTTP Server 2.4.55 through 2.4.70, plus standalone GitHub mod_h2 2.0.8 through 2.0.42. HTTP/2 support itself arrived in 2.4.17, so a 2.4 server older than 2.4.55 is outside this bug’s httpd range even though the module existed, unless it loads a standalone mod_h2 build from the affected GitHub series.

How Do You Disable HTTP/2 on Apache Until You Can Patch?

Set Protocols http/1.1 in every config that currently lists h2 or h2c, including virtual hosts, then restart httpd so the running process drops the old module. Red Hat says modern browsers and API clients fall back to HTTP/1.1 with no client-side change, at the cost of sequential file delivery and uncompressed headers, and that curl -kI –http2 should then print HTTP/1.1 200 rather than HTTP/2 200.

What Else Did Apache HTTP Server 2.4.71 Fix?

CVE-2026-106023, rated important, is a NULL pointer crash in mod_md on 2.4.30 through 2.4.70, reported by hexb1n, Yang Song, and JiaSheng He of 360 Vulnerability Research Institute with 360 TuLongFeng, plus Lucian Nitescu and Bartlomiej Dmitruk. CVE-2026-109163, rated low, is a one-byte stack overwrite in mod_vhost_alias that only hits 2.4.69 and 2.4.70 and is a leftover after CVE-2026-63292.

Who Discovered the mod_http2 Remote Code Flaw?

Anthropic’s OSS Scanner reported it on October 26, 2026, under tracker id ANT-2026-MAPKT6MZ, and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported it independently on November 3. Apache published the fix in 2.4.71 on November 11, 16 days after the first report.

Are Ubuntu 18.04 and Red Hat Enterprise Linux 8 Affected?

No. Ubuntu marks 18.04, 16.04, and 14.04 as not affected, and Red Hat marks RHEL 8 and RHEL 7 as not affected because the vulnerable code is not present. Ubuntu 20.04 is affected, and its fix (2.4.41-4ubuntu3.23+esm11) ships only through Ubuntu Pro. RHEL 9 and 10 are affected through the separate mod_http2 package, not through an httpd 2.4.71 NVR.

Harry is the editor of WORLDHAB, an independent publication that he owns and edits himself. His decade in journalism started in reporting and moved into editing, and it left him with a short list of promises that readers can expect every article here to keep. Sources are named and linked, so a claim about a company, a government or a team can be traced to the statement, filing or transcript it came from. Dates are given in full, figures are checked against the original table before publication, and where a number is an estimate the story says whose estimate it is. Headlines describe what happened rather than tease it. Those expectations hold across all ten sections WORLDHAB publishes for an international audience: news, business, technology and science on one side, sports, entertainment, lifestyle and travel on another, with auto and gaming covered with the same seriousness. Harry keeps a public corrections policy and marks every change on the article it affects. Reader mail is read by him and answered from support@worldhab.com.

Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Trending