Apache mod_http2 CVE-2026-119618 Now Reported Exploited: Singapore CERT Warns of Active Attacks and a Public PoC — Update to 2.4.71 or Set Protocols http/1.1

Critical · 2026-11-18 · By H.A

Apache mod_http2 CVE-2026-119618 Now Reported Exploited: Singapore CERT Warns of Active Attacks and a Public PoC — Update to 2.4.71 or Set Protocols http/1.1

Singapore's CSA says the unauthenticated mod_http2 race-condition RCE in Apache HTTP Server 2.4.55–2.4.70 is reportedly being exploited with a public proof of concept, a week after the 2.4.71 fix.

Overview

A week after Apache released HTTP Server 2.4.71, the critical mod_http2 flaw it fixed, CVE-2026-119618, has moved from "patch soon" to "patch now". On 17 November 2026, Singapore's Cyber Security Agency (CSA) published alert AL-2026-164, "Active Exploitation of Vulnerability in Apache HTTP Server's mod_http2". It says the vulnerability is "reportedly being actively exploited, and a proof-of-concept exploit is publicly available", and tells organisations to update immediately.

We covered the patch release on 14 November. This is what has changed since then:

CSA has not said who is attacking, where the attacks were seen or how many servers were hit. When we checked on 18 November, CISA had not added the CVE to its Known Exploited Vulnerabilities (KEV) catalog. Treat the exploitation report as credible but not yet confirmed by other sources. Either way, internet-facing Apache servers that speak HTTP/2 should be patched or reconfigured today.

The Vulnerability

CVE-2026-119618 is a race condition (concurrent execution using a shared resource with improper synchronisation) in the assign_headers() function of mod_http2, the module that gives Apache HTTP/2 support. Red Hat describes it as a thread-safety flaw: one thread writes into memory that another thread owns. A worker thread handling a stream corrupts memory belonging to the connection thread through an allocator shared without a lock. The heap corruption can lead to remote code execution, and the attacker needs no login. They only have to send crafted, concurrent HTTP/2 requests.

Researchers who analysed the one-line fix (commit 824beab) say the trigger is a request that carries a Content-Type header but no Content-Length and no body. mod_http2 then writes a Content-Length: 0 header into the connection's shared header table instead of the stream's private copy. Any code that runs this way runs as the web server account (www-data, apache). Getting root would need a second, local flaw.

Affected and unaffected versions:

Severity scores differ. Red Hat gives 9.8 (CVSS 3.1, low attack complexity). The CVE record carries 8.1 because it rates attack complexity as high, reflecting the race. Red Hat lowers its rating to Important on RHEL 9 and 10, because their mod_http2 packages give each HTTP/2 stream its own allocator, which makes exploitation much harder.

Timeline

Tradecraft

No attack details have been published. Based on how the bug works, attackers are likely to:

Because winning the race is unreliable, failed attempts are likely to leave crashed Apache child processes in the logs. That makes them worth hunting for.

Detection

Find out whether a server is exposed:

apachectl -M 2>/dev/null | grep -i http2
grep -rn "^\s*Protocols" /etc/apache2/ /etc/httpd/ 2>/dev/null
curl -skI --http2 https://your-server.example/ | head -1   # "HTTP/2" = h2 negotiated

Hunt for signs of exploitation attempts and follow-on activity:

Check fixes against package changelogs or vendor advisory IDs, not version banners. Backported fixes make banner-based scanners unreliable in both directions.

Recommended Actions

Protocols http/1.1

Analyst Assessment

We rate this High to Critical for any organisation running internet-facing Apache with HTTP/2. Apache is one of the most widely deployed web servers, HTTP/2 is turned on by default in many distribution and hosting configurations, and the bug needs no login. The race condition, and the per-stream allocators on RHEL 9 and 10, make reliable exploitation harder. That explains the split between the 9.8 and 8.1 scores. But public exploit claims, Red Hat's statement that a reliable default-configuration exploit has been shown, and a national CERT's exploitation report together leave little room to wait.

The case also shows how quickly the window now closes. AI-assisted vulnerability discovery found the bug first, a second team found it within days, and the fix was public for less than a week before exploitation was reported. Expect broader scanning and a possible CISA KEV listing soon. Defenders should check their HTTP/2 exposure with real protocol probes, not module inventories.

Sources

REEF SENTINEL