Singapore CERT Reports Apache HTTP2 Flaw Under Exploitation
Singapore's Cyber Security Agency said on November 17 that CVE-2026-119618, a race condition in Apache HTTP Server's mod_http2 module, is reportedly being actively exploited, and it told administrators to update to version 2.4.71 immediately.
Edited and fact-checked by Stephen Sprague
Apache fixed CVE-2026-119618 in version 2.4.71 on November 11, and Singapore's CSA reported exploitation on November 17.
Singapore's Cyber Security Agency published alert AL-2026-164 on November 17 and used the word exploited. The alert covers CVE-2026-119618, a vulnerability in mod_http2, the module that gives Apache HTTP Server its HTTP/2 support, and the agency says the flaw is "reportedly being actively exploited, and a proof-of-concept exploit is publicly available."
The defect is a race condition, tracked as CWE-362, in the assign_headers() function, where two threads work on shared header data without proper synchronization and the resulting heap corruption can give an attacker remote code execution without a login. Only servers with mod_http2 enabled, running the h2 or h2c protocol, can be reached through it, and servers that do not offer HTTP/2 are not exposed.
Apache HTTP Server versions 2.4.55 through 2.4.70 are affected, along with standalone mod_h2 versions 2.0.8 through 2.0.42, and Apache fixed the flaw in version 2.4.71 on November 11, six days before the exploitation alert. The scores attached to the flaw disagree, with the CVE record rating it 8.1 at high attack complexity, Red Hat rating it 9.8, and Apache's own security page for the 2.4 series rating the bug critical.
The alert does not name a victim, an attacker, or a count of compromised servers, and no security company has published attack details, while CISA had not added the CVE to its Known Exploited Vulnerabilities catalog when the alert was checked on November 18. A national CERT reports exploitation and a public proof of concept exists, and the independent confirmation has not been published yet, which is the honest state of the record.
The fix is a server update that cannot arrive through a website plugin or theme, so administrators should move affected servers to Apache HTTP Server 2.4.71 or a vendor package carrying the backported fix, or turn off HTTP/2 until the update is in. The flaw was found independently by Anthropic's OSS Scanner and by Google Cloud researchers Anthony Weems and Simon Scannell, and it sat in released code from January 2023, when version 2.4.55 shipped, until the November fix.
The conversation.
Loading comments…
A little more perspective.
Reading is free. Verified members can comment and reply for $2 a month.