HTTP/2 Bomb CVE-2026-49975: A Flaw Detonates Apache HTTP Server

Red | Vulnerability
Download Now
CVE-2026-49975: HTTP/2 Bomb — Apache HTTP Server DoS Vulnerability | Threat Advisory TA2026164
HiveForce Labs  ·  Threat Advisory  

HTTP/2 Bomb CVE-2026-49975: A Flaw Detonates Apache HTTP Server

A remote, unauthenticated denial-of-service vulnerability in Apache HTTP Server's mod_http2 module — tracked as CVE-2026-49975 — combines an HPACK compression bomb with a flow-control stall to exhaust server memory at a 4,000:1 amplification ratio. A single attacker on a 100 Mbps connection can consume 32 GB of server memory in approximately 18 seconds, rendering internet-facing Apache instances inaccessible. Proof-of-concept code is already public. Patch to mod_http2 v2.0.41 immediately.

⚠ THREAT LEVEL: RED  ·  PUBLIC PoC AVAILABLE AS OF JUNE 2, 2026  ·  NO AUTHENTICATION REQUIRED  ·  ZERO-DAY: NO  ·  CISA KEV: NO  ·  PATCH AVAILABLE: YES — mod_http2 v2.0.41
⚠ Threat Level: Red CVE-2026-49975 CWE-400 · Uncontrolled Resource Consumption Apache HTTP Server · mod_http2 DoS · Memory Exhaustion Patch Available: mod_http2 v2.0.41 PoC Public: June 2, 2026 Published: June 12, 2026
CVE ID
CVE-2026-49975
TA Number
TA2026164
Threat Level
Red
Affected Product
Apache HTTP Server mod_http2
Fixed Version
mod_http2 v2.0.41
CWE
CWE-400
Attack Type
DoS · Memory Exhaustion
First Seen
June 2, 2026
Admiralty Code
A1
4,000:1
Memory Amplification Ratio
per empty cookie stream
~18 sec
Time to exhaust 32 GB
Apache httpd 2.4.67 (single client)
100 Mbps
Minimum connection needed
to render server inaccessible

Summary

CVE-2026-49975 represents a direct and immediate threat to the availability of internet-facing Apache HTTP Server deployments with HTTP/2 enabled. The vulnerability, classified under CWE-400 (Uncontrolled Resource Consumption), is not a misconfiguration — it abuses default HTTP/2 protocol behavior, meaning any exposed Apache instance running mod_http2 prior to version v2.0.41 is potentially vulnerable with no additional preconditions.

The most damaging operational outcome is not necessarily an outright server crash. An attacker can deliberately hold memory pressure just below the out-of-memory kill threshold to push the host into swap thrashing, degrading every workload on the machine rather than triggering a clean worker respawn. With proof-of-concept code publicly available since June 2, 2026, the barrier to exploitation is critically low. The resulting outages of public websites, APIs, and gateways carry meaningful service-disruption, reputational, and financial consequences.

The sibling vulnerabilities affecting other HTTP/2 implementations have received separate identifiers: Envoy (CVE-2026-47774) and Microsoft IIS (CVE-2026-49160). Cloudflare reports its existing architecture already mitigates the attack. This advisory covers only the Apache HTTP Server (mod_http2) variant, CVE-2026-49975, disclosed to Apache on May 27, 2026.


CVE Reference

CVE ID Vulnerability Name Affected Products Affected CPE CWE ID Zero-Day CISA KEV Patch
CVE-2026-49975 HTTP/2 Bomb (Apache HTTP Server Denial-of-Service Vulnerability) Apache HTTP Server (httpd) with mod_http2 and HTTP/2 enabled, prior to mod_http2 v2.0.41 (e.g., 2.4.67) cpe:2.3:a:apache:http_server:*:*:*:*:*:*:*:* CWE-400 ✗ No ✗ No ✓ Yes

Vulnerability Details

The HTTP/2 Bomb attack combining HPACK compression exploitation with a flow-control stall creates a novel and highly efficient memory-exhaustion vector in Apache HTTP Server. The five stages below document the complete attack mechanics of CVE-2026-49975.

#1
The HTTP/2 Bomb — HPACK Compression Bomb + Flow-Control Stall
The HTTP/2 Bomb, discovered via the OpenAI Codex agent, combines two known techniques into a single efficient memory-exhaustion attack against Apache HTTP Server. The first component is an HPACK compression bomb: HTTP/2's HPACK scheme allows a client to reference a stored header with a single wire byte, which the server must expand into a full allocated header copy — so one wire byte becomes one full server-side allocation, repeated thousands of times per request. The second component is a flow-control stall: the client advertises a zero-byte flow-control window, preventing the server from ever completing a response, then drips one-byte WINDOW_UPDATE frames to keep the connection alive and hold all allocated memory in place indefinitely. The flaw affects the default HTTP/2 configuration of most major web servers including nginx, Apache, Microsoft IIS, Envoy, and Cloudflare Pingora.
#2
CVE-2026-49975 Scope — Apache mod_http2 and Sibling CVEs
This advisory focuses specifically on CVE-2026-49975, the Apache HTTP Server (mod_http2) instance of the HTTP/2 Bomb flaw, which was disclosed to Apache on May 27, 2026. Related implementations of the same class of vulnerability received separate CVE identifiers: Envoy received CVE-2026-47774 and Microsoft IIS received CVE-2026-49160. Cloudflare has stated its existing infrastructure architecture already blocks the attack without a patch. Organizations running any of these products should verify the relevant advisory for their specific environment.
#3
Novel Amplification Mechanism — Empty Header Per-Entry Overhead Bypass
What distinguishes this attack from prior HPACK compression bombs is the source of amplification. Earlier HPACK bomb techniques stored a large header value and referenced it repeatedly — a known pattern that servers mitigated by capping total decoded header size. This attack inverts that approach: the referenced header is nearly empty, and memory damage comes from the per-entry overhead the server allocates around each reference. Because there is almost nothing to decode, the existing decoded-header size cap never triggers, rendering the established defense ineffective against CVE-2026-49975.
#4
Apache-Specific Severity — Cookie Crumb Handling & LimitRequestFields Bypass
The impact on Apache HTTP Server is especially severe due to its cookie handling behavior. HTTP/2 allows a cookie to be split into many small fragments called "crumbs." Apache rebuilds the entire merged cookie string on every individual crumb received, while leaving each older in-progress copy in memory until the stream closes. Critically, these cookie crumbs are not counted against the LimitRequestFields limit — the exact control designed to stop the original HPACK bomb — creating a complete bypass. The result is approximately 4,000:1 memory amplification even with an empty cookie. In testing against Apache httpd 2.4.67, a single attacker client consumed and held approximately 32 GB of server memory in roughly 18 seconds.
#5
Exploitation Status — Public PoC Available, Short Gap to Active Exploitation
As of this advisory, there is no confirmed evidence of exploitation in the wild, and no specific threat actor or malware family has been attributed to CVE-2026-49975. However, working proof-of-concept code became publicly available on June 2, 2026, and the public fix commits in the Apache repository directly reveal the exploit technique. The gap between public disclosure and a deployable weapon is now critically short. The official fix ships in mod_http2 v2.0.41, which enforces that cookie crumbs count against the LimitRequestFields limit, closing the bypass that enables the 4,000:1 amplification.

Recommendations

The following prioritized mitigations should be applied to all Apache HTTP Server instances with HTTP/2 enabled. Patching is the only complete remediation for CVE-2026-49975; all other measures are partial stopgaps.

01
Update mod_http2 to v2.0.41 Immediately — Only Complete Remediation
Upgrade to mod_http2 v2.0.41 or later, available from the standalone mod_http2 releases. This version contains the official fix that makes cookie headers count against the LimitRequestFields limit, closing the amplification bypass. Patching is the only complete remediation for CVE-2026-49975 and must be treated as a priority for any Apache HTTP Server terminating HTTP/2 traffic from the internet — especially given that proof-of-concept code is already public.
02
Disable HTTP/2 Where Immediate Patching Is Not Possible
If upgrading mod_http2 cannot be completed in the short term, mitigate exposure immediately by setting Protocols http/1.1 in the Apache server configuration to disable HTTP/2. This removes the HTTP/2 Bomb attack surface entirely, at the cost of HTTP/2 performance benefits. This measure should be treated strictly as a temporary stopgap until mod_http2 v2.0.41 is deployed.
03
Apply Partial Hardening on Unpatched Servers via Memory Caps and Stream Limits
Lowering LimitRequestFieldSize reduces the per-stream blast radius by capping the merged cookie size and therefore the usable crumb count. This is a partial mitigation only — an attacker can still multiply the effect across many streams and connections. As a supplemental safety net, cap per-worker memory using cgroups, ulimit -v, or container resource limits tight enough that a bombed worker is OOM-killed and respawned before it drags the host into swap thrashing. Ensure stalled streams have a bounded lifetime regardless of WINDOW_UPDATE activity. Note: lowering LimitRequestFields alone provides no protection on unpatched versions, since duplicate cookie crumbs are not counted against it.
04
Front Internet-Facing Apache Servers with a Reverse Proxy or WAAP Layer
Place internet-facing Apache HTTP Server instances behind a reverse proxy, gateway, web application and API protection (WAAP) service, or Layer 7 load balancer that terminates public HTTP/2 sessions and enforces a hard cap on the number of header fields per request — including cookie crumbs — independent of their total decoded size. Combine this architecture with strict access controls that prevent direct connections to the origin Apache server from the public internet.

MITRE ATT&CK TTPs

The following MITRE ATT&CK tactics, techniques, and sub-techniques are associated with exploitation of CVE-2026-49975 in Apache HTTP Server.

Tactic Technique ID Sub-technique ID Description
Initial Access T1190 Exploit Public-Facing Application — attacker sends crafted HTTP/2 requests to internet-exposed Apache HTTP Server instances with mod_http2 enabled
Execution T1059 Command and Scripting Interpreter — publicly available proof-of-concept scripts used to send HPACK compression bomb requests with flow-control stalls against vulnerable Apache targets
Impact T1499 T1499.003 — Application Exhaustion Flood Endpoint Denial of Service — HTTP/2 HPACK compression bomb with cookie crumb amplification exhausts Apache worker memory; 4,000:1 ratio achieved with a single client connection
Impact T1499 T1499.001 — OS Exhaustion Flood Endpoint Denial of Service — sustained memory pressure via zero-byte flow-control windows and WINDOW_UPDATE drip pushes host into swap thrashing, degrading all system workloads

Patch Links


References