Apache Patches Critical RCE Flaw CVE-2026-119618 in mod_http2

A critical heap-corruption bug in Apache httpd's mod_http2 module can lead to remote code execution. Version 2.4.71 patches it.

The Apache HTTP Server feather logo
The Apache HTTP Server project logo. Image: The Apache Software Foundation.
Key facts
  • What: CVE-2026-119618, a critical heap-corruption flaw in Apache HTTP Server's mod_http2 module, can lead to remote code execution.
  • Who's affected: Apache HTTP Server 2.4.55 through 2.4.70 with mod_http2 enabled, and the standalone GitHub mod_h2 module versions 2.0.8 through 2.0.42.
  • Fix: Apache HTTP Server 2.4.71, released November 11, 2026, patches the bug along with two lower-severity flaws.
  • Severity: Rated "critical" by the Apache Software Foundation; NVD lists a CVSS v3.1 base score of 8.1 (High).
  • Found by: Two independent reports — Anthropic's automated open-source scanner and Google Cloud's Vulnerability Research team.

Apache HTTP Server, the web server software that still runs a significant share of the internet's sites, shipped version 2.4.71 on November 11, 2026, to close a critical remote-code-execution hole in its mod_http2 module. The flaw, tracked as CVE-2026-119618, lives in a function called assign_headers() and stems from a race condition the Apache Software Foundation (ASF) describes as "concurrent execution using shared resource with improper synchronization." In plain terms: when multiple HTTP/2 threads touch the same header-assignment memory at the same time without proper locking, the result can be heap corruption that an attacker can turn into arbitrary code execution on the server.

What happened with CVE-2026-119618

The Apache Software Foundation's official security advisory page lists CVE-2026-119618 as the headline fix in the 2.4.71 release, rating it "critical" — the top tier in the ASF's own three-level system (critical, important, low) for httpd vulnerabilities. The bug affects any server running mod_http2, the module that handles HTTP/2 protocol negotiation and header processing, between versions 2.4.55 and 2.4.70 inclusive. Because mod_http2 ships as a default, commonly enabled module in most Linux distributions' Apache packages, the practical exposure extends to a large slice of the internet's HTTP/2-capable web servers.

NVD's National Vulnerability Database entry assigns the flaw a CVSS v3.1 base score of 8.1, in the "High" band, with a vector of AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H — network-exploitable, no privileges or user interaction required, but with high attack complexity, and full impact on confidentiality, integrity, and availability if successfully triggered. The gap between the ASF's "critical" label and NVD's "High" CVSS banding is not unusual; vendors and NVD sometimes weigh severity slightly differently, and both figures are published directly by their respective sources rather than estimated here.

How the mod_http2 flaw works

HTTP/2 allows a single TCP connection to carry many concurrent request streams, which means the module handling it has to juggle shared memory structures across multiple execution contexts at once. According to the Apache advisory, assign_headers() — the function responsible for attaching parsed header data to an HTTP/2 request — did not properly synchronize access to that shared memory when multiple streams were processed concurrently. A specially timed sequence of HTTP/2 requests can win the resulting race condition and corrupt heap memory, a class of bug (CWE: improper synchronization) that security researchers have long flagged as one of the more dangerous and harder-to-spot categories in C-based network daemons, in the same family of memory-safety issues that have driven high-profile fixes in other widely used open-source server software.

Because the race condition requires precise timing, the ASF classifies attack complexity as "high" rather than "low" — exploitation isn't trivial, but it also isn't theoretical. The advisory does not list the bug as requiring authentication or any user interaction, which is why it still earns a critical label despite the complexity caveat.

Who found the bug

The Apache advisory credits two separate discoveries. The first report, filed October 26, 2026, came from an automated scanning tool the advisory identifies as "Anthropic's OSS Scanner," tracked internally under the identifier ANT-2026-MAPKT6MZ. A second, independent report followed on November 3, 2026, from Anthony Weems and Simon Scannell of Google Cloud's Vulnerability Research team. Two unrelated research efforts landing on the same bug within about a week of each other is a pattern security teams typically read as a signal that a flaw is discoverable enough to warrant fast patching — the kind of bug that, once public, invites copy-cat hunting by less well-intentioned researchers too.

Apache credited both reports, and its public commit history shows the fix landed on November 11, 2026, under commit 824beab in the official httpd source repository, the same day 2.4.71 shipped.

Affected versions and what's patched

Apache HTTP Server 2.4.71 bundles fixes for three CVEs in total — the critical mod_http2 bug plus two lesser issues disclosed in the same advisory:

CVEComponentSeverityAffected rangeFixed in
CVE-2026-119618mod_http2 (assign_headers)Critical2.4.55 – 2.4.702.4.71
CVE-2026-106023mod_mdImportant2.4.30 – 2.4.702.4.71
CVE-2026-109163mod_vhost_aliasLow2.4.69 – 2.4.702.4.71

The companion mod_md issue (CVE-2026-106023) is a NULL pointer dereference during HTTP request processing that can crash a child worker process — a denial-of-service risk rather than code execution, but one the ASF still rates "important." The third, CVE-2026-109163, is a one-byte stack buffer overwrite in mod_vhost_alias affecting only the two most recent prior releases, 2.4.69 and 2.4.70, and is rated "low."

Separately, the GitHub-hosted standalone mod_h2 module — the upstream project the bundled mod_http2 code derives from — carries the same CVE-2026-119618 exposure in its own versions 2.0.8 through 2.0.42. Administrators running that standalone module rather than the version bundled with httpd should check the project's release notes and update independently, since it is versioned and released separately from Apache HTTP Server itself.

Is CVE-2026-119618 being actively exploited?

As of this writing, CVE-2026-119618 does not appear in the CISA Known Exploited Vulnerabilities (KEV) catalog, which tracks vulnerabilities CISA has confirmed are being exploited in the wild. That absence is not a guarantee of safety — KEV listings lag real-world exploitation by definition, since CISA can only add a CVE once it has evidence of active abuse — but it does mean there is currently no confirmed in-the-wild exploitation tied to this specific CVE from CISA's public record. Given that the bug was reported responsibly by two research teams rather than discovered through incident response, and that proof-of-concept exploitation requires winning a timing-sensitive race condition, security teams are treating this as a "patch now, before public exploit code circulates" situation rather than an active-breach one.

That calculus can change quickly. Earlier in November, CISA added a different widely deployed open-source server component, OpenSSH, to its KEV catalog within days of its flaw becoming public knowledge, and a similarly compressed timeline played out when UnrealIRCd's delimiter-handling flaw earned a fast-tracked federal patch deadline after being added to the catalog. Internet-facing server software with a large install base is a routine target for rapid weaponization once technical details are public, which is precisely why the ASF, NVD, and downstream Linux distributions pushed advisories and packages within hours of the November 11 release.

Why an Apache httpd bug matters at this scale

Apache HTTP Server has been one of the most widely deployed web server platforms since the 1990s, and it remains a default or optional component across virtually every major Linux distribution, many managed hosting platforms, and countless embedded and appliance products that bundle a web management interface. A critical, unauthenticated, network-reachable RCE in a module as commonly enabled as mod_http2 — the module responsible for modern HTTP/2 traffic — has the kind of broad surface area that security teams prioritize regardless of how complex the exploitation path is rated, because "high complexity" at the vendor level can still mean "trivial for a well-resourced attacker with a working exploit chain."

Downstream distributions moved quickly. Red Hat, Ubuntu, Gentoo, AlmaLinux, and Microsoft's Azure Linux all published or tracked their own advisories and patch issues referencing CVE-2026-119618 within days of the ASF's disclosure, reflecting how a single upstream httpd fix cascades into dozens of separate distro-level package updates that administrators running Apache via a Linux distribution's own packages need to pull in rather than compiling from source themselves.

The exposure isn't limited to traditional web hosting. Apache httpd ships embedded inside a long list of network appliances, management consoles, and self-hosted application stacks that bundle it as a front-end web server, often without the operator even realizing which web server binary is running underneath a vendor's branded interface. That makes a full inventory step — not just patching the servers an organization knows about, but checking appliances, management interfaces, and vendor-supplied virtual machines for a bundled httpd install — part of a thorough response to this advisory, since mod_http2 is enabled by default in most common packaging.

How to patch and mitigate

The ASF's guidance is straightforward: upgrade to Apache HTTP Server 2.4.71 or later. There is no supported configuration workaround published in the advisory for disabling only the vulnerable code path while keeping HTTP/2 active, so administrators who cannot immediately upgrade should weigh temporarily disabling mod_http2 (forcing clients back to HTTP/1.1) against the operational cost of doing so, pending the update. Organizations should:

  • Check their httpd version with httpd -v or apachectl -v and confirm it is 2.4.71 or newer.
  • Pull the updated package through their Linux distribution's package manager — Red Hat, Ubuntu, Debian-derivatives, Gentoo, and AlmaLinux have each published or are tracking their own advisories tied to this CVE.
  • If running the standalone GitHub mod_h2 module rather than the bundled version, update that component separately, since it is not versioned alongside Apache HTTP Server releases.
  • Where an immediate upgrade isn't possible, evaluate temporarily disabling mod_http2 on internet-facing instances as a stop-gap, understanding the HTTP/2 performance and multiplexing benefits that will be lost in the meantime.
  • Review web server logs for unusual HTTP/2 stream patterns or crash loops on affected hosts as a basic triage step, even though the ASF advisory does not describe a simple indicator-of-compromise signature for this bug.
  • Inventory appliances, management consoles, and vendor appliances that may bundle Apache HTTP Server internally rather than assuming only directly-managed web servers are in scope.

Organizations running a web application firewall (WAF) in front of affected servers should check with their WAF vendor for a virtual-patch rule covering CVE-2026-119618, though the ASF advisory itself does not publish a specific detection signature, and a WAF rule should be treated as a stop-gap rather than a substitute for the 2.4.71 upgrade. Hosting providers and managed WordPress, Drupal, or other CMS platforms that run on Apache behind the scenes should also confirm with their provider whether the underlying infrastructure has already been patched, since many customers of managed hosting have no direct control over the web server version their sites run on.

Timeline of the disclosure

DateEvent
Oct. 26, 2026Anthropic's automated OSS scanner reports the mod_http2 flaw to the Apache security team.
Nov. 3, 2026Google Cloud Vulnerability Research independently reports the same class of issue.
Nov. 11, 2026Apache lands fix commit 824beab; httpd 2.4.71 ships with CVE-2026-119618, CVE-2026-106023, and CVE-2026-109163 patched.
Nov. 11–14, 2026Red Hat, Ubuntu, Gentoo, AlmaLinux, and Microsoft Azure Linux publish or open tracking advisories for downstream packages.
Nov. 17, 2026No confirmed in-the-wild exploitation listed in CISA's KEV catalog as of publication.

What's next

Expect the usual post-disclosure cadence: technical write-ups dissecting the race condition in more detail, scanner and exploit-development communities probing for a reliable proof-of-concept now that the patch itself reveals the vulnerable code path, and — if history with similarly broad open-source server flaws is a guide — a CISA KEV listing within days or weeks if evidence of active exploitation surfaces. Administrators running Apache HTTP Server with mod_http2 enabled should treat the November 11 update as a priority patch rather than a routine point release, confirm their version with httpd -v, and pull updated packages from their distribution's security channel now rather than waiting for a KEV deadline to force the issue.

Frequently asked questions

What is CVE-2026-119618?

CVE-2026-119618 is a critical vulnerability in Apache HTTP Server's mod_http2 module. A race condition in the assign_headers() function can cause heap corruption, which the Apache Software Foundation says can lead to remote code execution.

Which Apache HTTP Server versions are affected?

Versions 2.4.55 through 2.4.70 are affected when mod_http2 is enabled. The standalone GitHub mod_h2 module, versions 2.0.8 through 2.0.42, carries the same exposure. Apache HTTP Server 2.4.71, released November 11, 2026, contains the fix.

Is CVE-2026-119618 being exploited in the wild?

As of this writing, the CVE does not appear on CISA's Known Exploited Vulnerabilities catalog, meaning there is no confirmed active exploitation in CISA's public record. The flaw was reported by security researchers rather than discovered during an incident.

How do I patch the mod_http2 vulnerability?

Upgrade to Apache HTTP Server 2.4.71 or later. Administrators who cannot upgrade immediately can consider temporarily disabling mod_http2, and should pull updated packages from their Linux distribution's security channel, since Red Hat, Ubuntu, Gentoo, AlmaLinux, and Microsoft Azure Linux have all published or tracked their own advisories.

Who discovered the Apache mod_http2 flaw?

The Apache advisory credits two independent reports: one from an automated tool identified as Anthropic's OSS Scanner on October 26, 2026, and a second from Anthony Weems and Simon Scannell of Google Cloud's Vulnerability Research team on November 3, 2026.

Sources

More on Apache HTTP Server →Apache HTTP ServerCVE-2026-119618mod_http2Remote Code ExecutionWeb Server Security
Sana Qureshi
Written bySana Qureshi

Sana Qureshi runs the security and privacy desk. She reports on actively exploited vulnerabilities, vendor patches and data breaches, and covers the password managers, VPNs and authentication tools readers use to protect themselves. Her alerts cite vendor advisories, CISA and the CVE record directly.

More from Security & Privacy

See all