Critical Apache HTTP/2 Flaw Lets Attackers Run Code With No Login — Patch to 2.4.71 Now

One of the most widely used web servers on the internet has a critical flaw, and the worst part is how little an attacker needs to exploit it: no account, no login, no special access — just a request sent over HTTP/2. On November 11, 2026, the Apache HTTP Server project released version 2.4.71 to fix CVE-2026-119618, a race condition in the mod_http2 module that can lead to remote code execution. If your servers run Apache with HTTP/2 enabled, this is a patch-now situation.

Apache powers a huge share of the web, from small business sites to large cloud deployments, and the exposure numbers are striking. According to Wiz Research, 64% of cloud environments contain resources vulnerable to this flaw, and 51% have publicly exposed instances. Those figures come with a caveat — they do not account for whether HTTP/2 is actually switched on — but they explain why security teams moved fast this week.

What CVE-2026-119618 Is

CVE-2026-119618 is a race condition — classified as CWE-362 — inside mod_http2, the module that gives Apache HTTP Server its HTTP/2 support. The bug sits in a function called assign_headers(), where two threads can race over a shared resource without proper synchronization. When the timing lines up the wrong way, the result is heap corruption, and from heap corruption an attacker can reach remote code execution.

Apache’s own advisory describes it plainly: a “concurrent execution using shared resource with improper synchronization vulnerability in Apache HTTP Server’s mod_http2 in assign_headers() can lead to RCE.” The project rates the flaw critical, and its 2.4.71 release notes list three fixed CVEs — one critical, one important, one low — with this one as the critical entry.

The most important detail for anyone triaging this is the trigger condition. The flaw is only reachable on servers that actually negotiate HTTP/2 — that is, servers whose Protocols directive includes h2 or h2c. Servers serving only HTTP/1.1 are not affected. That distinction matters, because it means the first question in any response is not “do we run Apache?” but “do we run Apache with HTTP/2 turned on?”

Which Versions Are Affected

The affected range is wide. Apache HTTP Server versions 2.4.55 through 2.4.70 are vulnerable, and the standalone mod_h2 package distributed from GitHub is affected from version 2.0.8 through 2.0.42. The fix is Apache HTTP Server 2.4.71, released November 11, 2026.

There is a small piece of good news for very old deployments: mod_http2 versions before 2.0.8 do not contain the vulnerable code, and Red Hat notes that Red Hat Enterprise Linux 8 and earlier are not affected. But anything in the 2.4.55–2.4.70 window with HTTP/2 enabled should be treated as exposed until it is patched.

How the Race Condition Works

Two streams of glowing data packets colliding in a burst of sparks, illustrating a race condition

A race condition is a timing bug, and timing bugs are some of the hardest flaws to reason about. In normal operation, mod_http2 uses a lock-free allocator to hand out memory for HTTP/2 streams. Two threads — a worker thread and a connection thread — can reach the same shared state in assign_headers() at the same moment, and without adequate synchronization one thread’s work can corrupt the memory the other thread is using.

That corruption is the heap damage Apache’s advisory title refers to. On its own, heap corruption usually crashes a process. In the hands of an attacker who can control the timing and content of requests, it becomes a path to running their own code inside the web server process — with whatever privileges that process holds. From there, the attacker has a foothold on the server, and in cloud environments that foothold can become a starting point for lateral movement toward adjacent services and cloud metadata endpoints.

It is worth noting what this bug is not. It lives in Apache’s own HTTP/2 implementation, not in any website or application the server happens to host. Your code can be perfectly secure and still be at risk if the server underneath it is vulnerable and HTTP/2 is enabled.

How Serious Is It? The Score Tells a Complicated Story

Here is where the story gets interesting, and where headlines have arguably been more confident than the underlying data. Apache itself published no CVSS score for this flaw. Its CVE record, filed with Apache as the assigning authority, reached the National Vulnerability Database on November 11 with an empty metrics object — no CVSS 4.0, no CVSS 3.1, no CVSS 2.0 from any source — and was still awaiting analysis the next day.

The 9.8 that ran in much of the coverage comes from Red Hat, which scored the flaw as a CVE Numbering Authority in its own right at CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H — network-accessible, low complexity, no privileges, no user interaction, with full impact on confidentiality, integrity and availability. CISA, meanwhile, rates it 8.1. The practical takeaway is the same whichever number you use: treat it as critical and patch, but know that the single most-quoted score is Red Hat’s assessment, not Apache’s or NVD’s.

Red Hat also adds nuance of its own. It rates its RHEL 9 and 10 builds as Important rather than Critical, because those packages allocate each HTTP/2 stream from a separate allocator, which raises the bar for exploitation. And Red Hat is the only primary source to state that public research has demonstrated a reliable exploit against a default-configured server with mod_http2 enabled.

Who Found It — and How Fast It Moved

The flaw was found independently by two teams, eight days apart. Anthropic’s OSS Scanner — an opt-in, model-driven scanner for open-source projects — reported it on October 26, 2026, under the identifier ANT-2026-MAPKT6MZ. Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research reported the same bug on November 3. Apache disclosed it publicly on November 11 at 12:19 UTC, and the CVE record was published later that day.

That timeline — discovery, quiet coordination, then a same-day patch and disclosure — is how responsible disclosure is supposed to work. It also means the window between public disclosure and active exploitation is the danger zone. The day after disclosure, a public proof-of-concept appeared on GitHub demonstrating the heap corruption, though it stops short of full code execution. As of November 13, no confirmed in-the-wild exploitation had been reported, and the flaw does not appear in CISA’s Known Exploited Vulnerabilities catalog. That status can change quickly, which is exactly why the patch guidance is urgent rather than advisory.

It is also worth distinguishing this flaw from an earlier mod_http2 issue, CVE-2026-23918, which affects only a single release. CVE-2026-119618 is the broader, more consequential one.

The Cloud Exposure Problem

Wiz’s numbers deserve a closer look, because they explain why this flaw got so much attention so fast. According to Wiz Research data, 64% of cloud environments have resources vulnerable to CVE-2026-119618, and 51% have publicly exposed instances — reachable from the internet without additional network controls in the way. See also the Censys advisory on this flaw.

Two caveats keep those numbers honest. First, Wiz states plainly that the figures do not take configuration into account: they count resources running vulnerable versions, not confirmed exploitable systems with HTTP/2 actually enabled. Second, a compromised Apache instance in a containerized or virtualized environment matters because of what sits next to it — adjacent microservices, internal APIs, and cloud metadata endpoints that a foothold can reach. The server is the entry point; the blast radius depends on the architecture around it.

This is also a reminder that the cloud makes patching both easier and harder. Easier, because images and instances can be rebuilt and redeployed quickly. Harder, because Apache is often buried inside container images, base layers and appliances that nobody has inventoried in years. If you are not sure which of your images carry a vulnerable httpd, that uncertainty is itself the finding.

What to Do Right Now

System administrator applying a security update shown as a green shield on a monitor

Start with inventory. Find every Apache HTTP Server instance you run — including the ones inside containers, appliances, and third-party images — and check two things: the version, and whether HTTP/2 is enabled. The command apachectl -V shows the version, and apachectl -M lists loaded modules; look for http2_module. The Protocols directive in your configuration tells you whether h2 or h2c is active.

Then patch. Upgrade Apache HTTP Server to 2.4.71 or newer. As of November 13, fixed packages are available for Debian 12 and 13, Ubuntu 22.04 through 26.10, Alpine, Fedora, Amazon Linux 2 and 2023, and Wolfi and Chainguard — but downstream packages can lag the upstream release, so confirm the build you are about to deploy actually carries the fix rather than assuming your distribution has caught up.

If you cannot patch immediately, you have a mitigation: turn off HTTP/2 by removing h2 and h2c from the Protocols directive and restarting the server. Apache itself publishes no workaround, so treat this as a temporary risk reduction while you schedule the update — not a substitute for it. And for the standalone mod_h2 package from GitHub, note that Apache had listed no fixed release as of November 12, so track that separately if you use it.

Finally, check for signs of trouble. A public proof-of-concept for heap corruption already exists, which means scanning and probing activity is a reasonable expectation even before any full exploit appears. Watch for unexpected httpd crashes, unusual child-process behavior, and any new outbound connections from your web servers. If you run a web application firewall, the usual HTTP/2 anomaly rules apply. Sysdig has published guidance on detecting heap corruption and RCE in this flaw.

Why This One Matters Beyond Apache

There is a bigger story inside this disclosure. The flaw was found by an AI-driven scanner — Anthropic’s OSS Scanner — and confirmed by a human research team eight days later. AI-assisted vulnerability discovery is now finding genuinely critical bugs in foundational open-source software, which means the pace of disclosure is only going to increase. The same tooling that finds these flaws for defenders will, sooner or later, be used by attackers to find them first.

That makes the boring fundamentals more important, not less: know what software you run, know which versions, patch quickly, and disable features you do not need. November has already been a busy month for patches — from a recent Linux kernel vulnerability to Microsoft’s November Patch Tuesday and Android’s November security update — and the pattern is clear. The teams that patch within days of disclosure are the ones that stay out of the headlines; the teams that wait are the ones that become case studies. If you run Apache with HTTP/2, update to 2.4.71 today. For more context, see our November’s exploited vulnerabilities roundup and our guide to cybersecurity threats to watch in 2026.

Frequently Asked Questions

Am I affected if my server only uses HTTP/1.1?

No. The flaw is only reachable when the server negotiates HTTP/2 through the Protocols directive. HTTP/1.1-only deployments are not vulnerable to CVE-2026-119618.

What is the fastest way to check my Apache version?

Run apachectl -V for the version and apachectl -M to see whether http2_module is loaded, then check the Protocols directive in your configuration for h2 or h2c. Anything in 2.4.55–2.4.70 with HTTP/2 enabled needs the 2.4.71 update.

Is there a workaround if I cannot patch right away?

Apache publishes no official workaround. The practical mitigation is to disable HTTP/2 by removing h2 and h2c from the Protocols directive until you can upgrade — but treat that as temporary, not a fix.

Has this flaw been exploited in the wild?

As of November 13, 2026, no confirmed in-the-wild exploitation had been reported, and the flaw is not in CISA’s Known Exploited Vulnerabilities catalog. A public proof-of-concept demonstrating heap corruption was posted on November 12, and Red Hat states that public research has demonstrated a reliable exploit against a default-configured server.

Does this affect the standalone mod_h2 module?

Yes. The standalone mod_h2 package from GitHub is affected from version 2.0.8 through 2.0.42. Apache had listed no fixed mod_h2 release as of November 12, so check for an updated release before assuming you are covered.

Leave a Comment

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

Scroll to Top