Apache fixes critical HTTP/2 flaw reported by Anthropic and Google
Apache HTTP Server 2.4.71 patches a critical mod_http2 bug that the project says can lead to remote code execution. Versions 2.4.55 through 2.4.70 are affected.
Key takeaways
- Apache HTTP Server 2.4.71, released Nov. 11, fixes CVE-2026-119618, a critical mod_http2 bug the project says can lead to remote code execution.
- Versions 2.4.55 through 2.4.70 are affected, as are some releases of the standalone mod_h2 module.
- Anthropic's OSS Scanner reported the flaw on Oct. 26, and Google Cloud Vulnerability Research researchers reported it on Nov. 3.
- SecurityOnline says no active attacks or public exploit code have been reported; Cyber Security News says the CVE entry has no public CVSS score yet.
- The release also fixes an important mod_md crash bug and a low-severity mod_vhost_alias bug.
The Apache HTTP Server project has released version 2.4.71 to fix a critical vulnerability in its HTTP/2 module that it says can lead to remote code execution. The flaw, tracked as CVE-2026-119618, affects Apache HTTP Server 2.4.55 through 2.4.70, according to the project's security advisory. Cyber Security News says the main risk is to servers with HTTP/2 enabled. The update came out on Nov. 11 and also fixes two less severe bugs.
What is the flaw?
Apache's advisory describes the bug as a concurrency problem in the assign_headers() function of mod_http2, where a shared resource is used without proper synchronization. The advisory's title refers to heap corruption and remote code execution, and its description says the bug "can lead to RCE." Cyber Security News explains that two parts of the code can work on the same memory at once, which can damage the heap.
Apache rates the bug critical. According to Cyber Security News, Apache reserves that rating for bugs that would let someone exploit a server remotely and execute their own code. The advisory says some releases of the standalone mod_h2 module distributed on GitHub are also affected.
Who found it?
The advisory credits two separate reports. Anthropic's OSS Scanner, which tracked it as ANT-2026-MAPKT6MZ according to the advisory, reported it to Apache's security team on Oct. 26. A second report came on Nov. 3 from Google researchers Anthony Weems and Simon Scannell, who work in its Cloud Vulnerability Research team. Cyber Security News describes the Google report as made independently. Apache shipped the fix on Nov. 11.
Is it being exploited?
SecurityOnline says no active attacks or public exploit code have been reported for any of the three flaws. Cyber Security News notes that the CVE record has only reserved status for now, meaning no CVSS score or full technical analysis has been published. NextFish has not independently verified whether the flaw has been exploited.
What else does 2.4.71 fix?
The release also fixes CVE-2026-106023, rated important, a NULL pointer dereference in mod_md that can crash a server child process during request handling. It affects versions 2.4.30 through 2.4.70. The third bug, CVE-2026-109163, is a low-severity one-byte stack buffer overwrite in mod_vhost_alias that affects only 2.4.69 and 2.4.70, according to the advisory.
The previous security release, 2.4.69 on Oct. 1, fixed 20 CVEs, according to the advisory.
What should administrators do?
Both outlets advise upgrading to 2.4.71 as soon as possible. Cyber Security News notes that Apache has not listed a workaround and suggests that operators who cannot upgrade right away could limit servers to HTTP/1.1 in the meantime, after testing the change. SecurityOnline suggests turning off mod_http2 and mod_md where they are not needed. Cyber Security News also notes that Linux distributions often backport security fixes while keeping the old version number, so administrators should read their vendor's advisory before concluding that a server is exposed. It also suggests watching logs for unusual crashes or worker-process restarts.
Disclosure: NextFish's AI drafting desk uses Claude, a model made by Anthropic.
Questions readers are asking
Which Apache versions are affected?
Apache HTTP Server 2.4.55 through 2.4.70, plus some releases of the standalone mod_h2 module, according to Apache's advisory.
Is there a workaround?
Apache has not listed one. Cyber Security News suggests limiting servers to HTTP/1.1 until they can be upgraded, and SecurityOnline suggests disabling mod_http2 and mod_md where they are not needed.
Who discovered the vulnerability?
Apache credits Anthropic's OSS Scanner, which reported it on Oct. 26, and Google researchers Anthony Weems and Simon Scannell, who filed their report on Nov. 3.
Is the flaw being exploited?
SecurityOnline says no active attacks or public exploit code have been reported for any of the three flaws fixed in 2.4.71.
Sources
- #apache
- #http2
- #vulnerability
- #remote-code-execution
- #patch
Get the day's top AI & tech stories on WhatsApp: Follow the NextFish channel
Get stories like this every morning.
Related
Cybersecurity4 min
ConnectWise urges ScreenConnect client updates as SCKit targets technicians
Microsoft, Huntress and Blackpoint have analysed the toolkit used against MSPs. It is built to jump to technicians, but researchers say they have not seen that work.
Cybersecurity3 min
Landmark Group says Shukran loyalty members' personal data was accessed
Names, contact details and dates of birth were involved, the Dubai retailer says, but not card details, passwords or points. It has not said how many members were affected.
Cybersecurity3 min
Operation Endgame takes down Gootloader, CastleRAT and StealC servers
The Justice Department says Gootloader infected at least 25,000 computers and was used against at least 44 US ransomware victims. Europol counts 235 servers hit in all.
Cybersecurity2 min
TSMC says leaked employee data matches records at a cloud provider
The chipmaker says its own systems show no sign of compromise after a seller offered a 6.9GB file of employee records on hacker forums for three bitcoin.