SecurityWeekEduard Kovacs
Apache fixes HTTP/2 flaw that could enable remote code execution
Part of the CVE-2026-119618 story · since 11 Nov
- Wed 11 Nov, 16:01 UTC. SecurityOnline, first report. Apache fixes HTTP/2 flaw that could enable remote code execution.
- Thu 12 Nov, 06:00 UTC. The Hacker News, its first report on the story. Apache fixes HTTP/2 flaw enabling unauthenticated remote code execution.
- Thu 12 Nov, 16:30 UTC. SecurityWeek, its first report on the story. Apache fixes HTTP/2 flaw that could enable remote code execution. This article, 3rd of 3.
Apache has patched a critical HTTP Server vulnerability that could allow unauthenticated remote code execution (RCE) on systems with HTTP/2 enabled, discovered independently by Anthropic and Google researchers. The flaw, tracked as CVE-2026-119618, affects Apache HTTP Server versions 2.4.55 through 2.4.70 and was addressed with the release of version 2.4.71 on 11 November 2026.
The issue resides in mod_http2, the module that handles HTTP/2 traffic, and stems from a race condition where multiple threads can improperly access shared resources, potentially leading to memory corruption.
Red Hat’s advisory describes a remote, unauthenticated exploit that could allow arbitrary command execution and control of the server process, assigning the vulnerability a CVSS score of 9.8. It notes that only servers with HTTP/2 enabled are affected; those serving only HTTP/1.1 are not vulnerable. Apache credited Anthropic’s OSS Scanner for reporting the flaw on 26 October, with Anthony Weems and Simon Scannell of Google Cloud Vulnerability Research independently reporting the same issue on 3 November.
Wiz reported that 64% of cloud environments in its data contained resources running affected Apache versions, and 51% had publicly exposed instances, though the firm cautioned that configuration details could affect exploitability. A publicly available PoC on GitHub documents memory corruption and Apache process crashes but does not demonstrate remote code execution.
Users are advised to upgrade to Apache HTTP Server 2.4.71 or apply vendor packages; disabling HTTP/2 can temporarily mitigate if immediate patching is not possible.
How the story developed
3 articles from 3 outlets since 11 Nov. Still developing; the latest report was 8 hours ago. This was the 3rd report, 1 day after the first.
- Wed 11 Nov, 16:01 UTC. SecurityOnline, first report. Apache fixes HTTP/2 flaw that could enable remote code execution.
- Thu 12 Nov, 06:00 UTC. The Hacker News, its first report on the story. Apache fixes HTTP/2 flaw enabling unauthenticated remote code execution.
- Thu 12 Nov, 16:30 UTC. SecurityWeek, its first report on the story. Apache fixes HTTP/2 flaw that could enable remote code execution. This article, 3rd of 3.
- CVE not in KEV
- No CVE
- Larger: an outlet’s first report
- Coverage over time
Show all 3 articles as a listHide the list
- Wed 11 NovDay 01
- Apache fixes HTTP/2 flaw that could enable remote code execution16:01 · SecurityOnline · First report
- Thu 12 NovDay 12
- Apache fixes HTTP/2 flaw enabling unauthenticated remote code execution06:00 · The Hacker News
- Apache fixes HTTP/2 flaw that could enable remote code execution16:30 · SecurityWeek · This article, 3rd of 3