CVE-2026-119618 is a critical flaw in the HTTP/2 module of the Apache HTTP Server that lets attackers corrupt memory in the server process without logging in and, in the worst case, run their own code. Versions 2.4.55 through 2.4.70 are affected when HTTP/2 is enabled. The Apache Software Foundation fixed the bug on November 11, 2026 with version 2.4.71. Anyone running Apache with HTTP/2 should update now or switch HTTP/2 off for the time being.
CVE-2026-119618: what is known about the flaw
According to the Apache HTTP Server project’s security page, the bug is a race condition in the assign_headers() function of mod_http2. The project describes it as “heap corruption and RCE” and rates it critical. Besides the Apache server itself, versions 2.0.8 through 2.0.42 of the separately distributed mod_h2 module from GitHub are affected as well.
The origin of the report stands out. According to Apache, Anthropic’s OSS Scanner reported the bug first, on October 26. On November 3, Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported the same flaw independently. The fix landed on November 11 and shipped the same day as version 2.4.71.
In its security bulletin RHSB-2026-017, Red Hat rates the flaw “Critical”; according to SecurityWeek, the vendor assigns it a CVSS score of 9.8. An attacker who can send HTTP/2 requests to an affected server needs neither credentials nor special privileges.
How the bug works
HTTP/2 multiplexes many parallel requests over a single connection, so mod_http2 hands those requests to worker threads. According to Red Hat, a worker thread can write into memory that belongs to the connection thread. Both use a shared memory allocator that is not adequately protected against concurrent access. The result is memory corruption inside the server process.
The fix itself is small: commit 824beab makes sure an internally added header is no longer written into the stream’s shared table but into the request’s own copy of the headers. The severity does not come from the size of the change but from the fact that the bug can be reached over the network without authentication.
Exploit status: proof of concept, no confirmed attacks
The signals on exploitation differ and are worth keeping apart:
- Red Hat says public research has demonstrated a reliable exploit against a server with
mod_http2enabled but, according to SecurityWeek, does not name the research. - A publicly available proof of concept on GitHub reproduces the memory corruption and Apache process crashes but does not demonstrate code execution.
- NHS England’s security centre reports a published proof of concept in its alert CC-4892 and assesses exploitation as likely.
- CVE-2026-119618 was not listed in CISA’s Known Exploited Vulnerabilities (KEV) catalog when we checked on November 13. We are not aware of reports of attacks in the wild so far.
That is no reason to relax. Even without working code execution, a proof of concept that crashes processes is enough to cause outages. And with memory bugs, the gap between a public crash PoC and a stable exploit is often only a few days.
How widespread affected systems are can only be estimated roughly. According to SecurityWeek, cloud security firm Wiz found resources running affected Apache versions in 64 percent of the cloud environments it sees, with publicly exposed instances in 51 percent. Wiz itself notes that these figures do not account for configuration, so they do not show how many servers actually have HTTP/2 enabled.
Who is affected and who is not
According to Red Hat, three conditions must be met: mod_http2 is loaded, the configuration includes h2 or h2c in a Protocols directive, and attackers can reach the server over HTTP/2. Servers that speak HTTP/1.1 only are not vulnerable.
At Red Hat, Red Hat Enterprise Linux 9 and 10 as well as JBoss Core Services 1 are directly affected; on RHEL 9 and 10, mod_http2 ships as a separate package. Debian has published package 2.4.71-1~deb12u1 for Bookworm and 2.4.71-1~deb13u1 for Trixie, as the Debian Security Tracker shows. Users of the standalone mod_h2 from GitHub should, according to NHS England, move to the HTTP/2 module built into Apache, because the repository was archived in June 2026.
The flaw sits in the web server, not in the application on top of it. Updates to WordPress, plugins or PHP frameworks do not help here, as WordPress security vendor Defiant also points out. Other web servers such as nginx or Caddy are not affected by this specific bug. If Apache runs as a backend behind a reverse proxy, what matters is whether the backend itself accepts HTTP/2.
What admins should do now
- Check version and configuration:
httpd -vorapache2 -vshows the version. Runninggrep -ri "Protocols"over the Apache configuration reveals whetherh2orh2cis enabled. - Update: install Apache 2.4.71 or your distribution’s patched package. For distribution packages, the package release counts, not the bare version number, because fixes are often backported.
- Rebuild containers: images that contain Apache must be rebuilt on the updated base image and redeployed. Updating the host is not enough.
- Interim fix: if you cannot patch right away, set
Protocols http/1.1and restart Apache. According to Red Hat, browsers and API clients fall back to HTTP/1.1 automatically; load times and bandwidth may rise somewhat. - Verify: with
curl -kI --http2 https://example.org, the first response line shows whether the server still speaks HTTP/2.
Version 2.4.71 also closes two more flaws: CVE-2026-106023 (rated important) is a NULL pointer bug in mod_md that can crash child processes and affects versions 2.4.30 through 2.4.70. CVE-2026-109163 (low) is a one-byte overflow in mod_vhost_alias in 2.4.69 and 2.4.70. So updating makes sense even if HTTP/2 is switched off.
Context: AI scanners find flaws in core infrastructure
An automated scanner from Anthropic reporting a critical bug in the Apache web server ahead of two experienced Google researchers fits a trend we have seen more often lately. Only days ago we covered the OpenSSH SSHole flaw, and web components such as Symfony HttpFoundation have also seen security updates in quick succession. For operators, this mainly means that the time between a fix and public knowledge of a bug is getting shorter, and patch routines have to keep up.
It also pays to look at the stack as a whole. If you recently updated plugins, as with the Contact Form 7 flaw CVE-2026-114432, you are covered at the application level but not at the web server level. Web server package updates therefore belong in the same maintenance plan as CMS and plugin updates.
Bottom line
CVE-2026-119618 deserves attention: rated critical, reachable without authentication and with a public proof of concept that causes crashes. There is no confirmed exploitation in the wild so far. The remedy is clear and quick to apply: install Apache 2.4.71 or your distribution update, rebuild containers and, where that cannot happen immediately, disable HTTP/2 temporarily.




