
Apache HTTP Server 2.4.71: How AI Caught a Critical Bug
Apache HTTP Server 2.4.71 fixes a critical mod_http2 flaw first reported by Anthropic's OSS Scanner, then by Google researchers. Here's how to update.
Some of the best security news is a bug found and fixed before attackers ever used it. Apache HTTP Server 2.4.71, released on November 11, patches a critical remote code execution flaw in the server's HTTP/2 module, and the Apache project credits Anthropic's OSS Scanner as the first to report it, with Google researchers independently finding the same issue a week later. It is a clear example of AI-assisted vulnerability discovery strengthening one of the most widely deployed pieces of software on the web.
- The fix: Apache HTTP Server 2.4.71, released November 11, 2026, resolves CVE-2026-119618 plus two lower-severity issues
- Affected: Versions 2.4.55 through 2.4.70, and only when HTTP/2 is enabled; HTTP/1.1-only servers are not affected
- Severity: Rated critical by Apache; Red Hat assigned a CVSS score of 9.8
- Finders: Anthropic's OSS Scanner (reported October 26) and Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research (reported November 3)
What Is CVE-2026-119618?
The flaw sits in mod_http2, the module that handles HTTP/2 traffic, specifically in its assign_headers function. Apache's advisory describes it as concurrent execution using a shared resource with improper synchronization, in plain terms a race condition where multiple threads touch the same memory without proper coordination. That can corrupt the heap and, in the worst case, let an unauthenticated remote attacker run code in the server process. The standalone mod_h2 module from GitHub, versions 2.0.8 through 2.0.42, is also affected.
The timeline is reassuring. According to SecurityWeek, Wiz said that when it published its analysis on November 11, no exploit was available and there were no reports of exploitation in the wild. A public proof of concept reproduces memory corruption and process crashes, but does not demonstrate code execution.
How Do You Fix the Apache mod_http2 Vulnerability?
The steps are simple:
- Update: Install Apache HTTP Server 2.4.71, or your Linux distribution's patched package
- Check HTTP/2: If you cannot patch right away, disabling HTTP/2 temporarily blocks this attack path, since HTTP/1.1-only configurations are not vulnerable
- Patch the platform, not the plugin: As SecurityWeek notes, WordPress and other application-level updates cannot fix this, because the bug lives in the web server underneath
Version 2.4.71 also fixes CVE-2026-106023, an important-rated crash in mod_md, and CVE-2026-109163, a low-severity stack buffer overflow, so it is worth rolling out promptly across the fleet. Wiz's data, as reported by SecurityWeek, found affected Apache versions in 64% of cloud environments it observes, though that figure does not account for whether HTTP/2 is actually turned on.
Why AI-Found Bugs Are Good News for Defenders
This is the pattern the security community has been hoping for. An automated AI scanner reported a subtle concurrency bug in a mature, heavily reviewed C codebase, and a skilled human research team confirmed it independently. Apache's advisory credits Anthropic's OSS Scanner by name under its own tracking ID, which shows the report went through normal coordinated disclosure.
Race conditions are notoriously hard to spot by reading code, because they depend on timing between threads. Tools that can reason about those interactions at scale give open-source maintainers more help than ever. We have seen similar momentum as AI models help harden the Linux kernel and as formal methods verify cryptographic protocols. The more of these bugs that get found by defenders first, the fewer that ever become incidents.
Bottom line: update to 2.4.71, confirm your HTTP/2 settings, and appreciate a case where the finders got there first. For more defensive security news, visit our AI security section.
Sources: Apache HTTP Server 2.4 security advisories — November 11, 2026; SecurityWeek — November 12, 2026.
More Ai Security Stories

Apple Secure Exclaves: How Your Camera Data Stays Private
Apple's Secure Exclaves keep raw camera and mic data away from the main OS, apps and Apple itself. Here is how the 3-part design protects ambient sensing.

Daybreak Red Team and Defense Factory: How AI Pen Tests Work
OpenAI's Daybreak Red Team and Defense Factory pair AI pen testing with automated patching. Here's how the 2 new security agents find, fix and retest.

Project Zero Full 90 Policy: What Faster Disclosure Means
Google Project Zero's Full 90 policy drops the 30-day patch grace period and moves to 60 days in 2027 and 30 in 2028. Here's what defenders should do.
