Skip to main content
Mallory
Back to intelligence
internet-facing-service-vulnerabilitywidely-deployed-product-advisoryoperational-disruption

HTTP/2 Bomb DoS Flaw Hits Apache, nginx, IIS, Envoy, and Pingora

Updated 7h agoFirst seen Jun 2, 202616 sources

Researchers publicly disclosed HTTP/2 Bomb, a remote denial-of-service technique that affects major web servers including Apache httpd, nginx, Microsoft IIS, Envoy, and Cloudflare Pingora under default HTTP/2 configurations. The attack combines HPACK header-compression amplification with an HTTP/2 flow-control stall, letting a low-bandwidth client trigger large memory allocations on the server and keep that memory pinned long enough to degrade or deny service. The disclosure says a single client on a 100 Mbps connection can make vulnerable servers inaccessible within seconds, with Apache httpd and Envoy observed consuming roughly 32 GB of memory in about 20 seconds.

Apache assigned the issue CVE-2026-49975, and the disclosure says nginx and Apache were privately notified before publication. Reported mitigations include upgrading nginx to 1.29.8 or later, using mod_http2 v2.0.41 for Apache, or disabling HTTP/2 where patches are not available. The researchers said limiting decoded header size alone is not enough; affected servers also need hard caps on header count and protections against long-lived stalled streams that retain memory. At the time of disclosure, fixes were reported for nginx and Apache, while IIS, Envoy, and Pingora reportedly had no patch available.

Share:
HTTP/2 Bomb DoS Flaw Hits Apache, nginx, IIS, Envoy, and Pingora
Stay ahead

Get ahead of threats like this

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.

EVENT TIMELINE

How this story unfolded

6 events from the most recent confirmed update back to the earliest known activity.

6 EVENTS
Jun 4, 20262d ago

Cloudflare and Microsoft issue responses on HTTP/2 Bomb impact

Cloudflare said Pingora does not require a patch because its architecture and DDoS protections already mitigate the HTTP/2 Bomb technique. Microsoft said it was investigating mitigations for IIS, while researchers advised unpatched IIS and Pingora users to disable HTTP/2 if possible or limit HTTP headers per request.

OpenAI's Codex chains decade-old DoS techniques into HTTP/2 Bomb
Jun 3, 20263d ago

HTTP/2 Bomb exploit PoC and impact details published

A follow-up report publicly shared exploit proof-of-concept details for HTTP/2 Bomb, describing how HPACK amplification and a zero-byte flow-control window can pin large memory allocations. The report said a single client could hold about 32 GB of memory on Apache httpd and Envoy in roughly 20 seconds and estimated more than 880,000 internet-exposed systems may be vulnerable.

HTTP/2 Bomb Exploit Details and PoC Publicly Disclosed
Jun 2, 20264d ago

Apache assigned CVE-2026-49975 and published mitigations

The oss-sec disclosure says Apache assigned CVE-2026-49975 to the issue and identified mitigations including using mod_http2 v2.0.41 for Apache. It also noted nginx users should upgrade to 1.29.8 or later, or disable HTTP/2 where patches are unavailable.

oss-sec: HTTP/2 Bomb affects Apache httpd, nginx, envoy, & pingora

HTTP/2 Bomb vulnerability publicly disclosed on oss-sec

A public disclosure described "HTTP/2 Bomb," a remote denial-of-service technique affecting default HTTP/2 configurations in nginx, Apache httpd, Microsoft IIS, Envoy, and Cloudflare Pingora. The writeup said the attack combines HPACK amplification with HTTP/2 flow-control stalling to trigger severe memory exhaustion.

oss-sec: HTTP/2 Bomb affects Apache httpd, nginx, envoy, & pingora

Researchers privately notified nginx and Apache of HTTP/2 Bomb

The disclosure states that nginx and Apache were privately notified about the HTTP/2 Bomb denial-of-service issue before the public release. No specific notification date is provided in the references.

oss-sec: HTTP/2 Bomb affects Apache httpd, nginx, envoy, & pingora
Feb 6, 20264mo ago

Envoy and H2O publish HTTP/2 Bomb fixes and mitigations

An oss-sec follow-up reported that Envoy assigned CVE-2026-47774 to a high-severity HTTP/2 denial-of-service issue tied to cookie header accounting and HPACK amplification, and said additional patches had been released by Envoy. The same discussion said H2O released mitigations for related HTTP/2 state amplification and stalled-stream retention issues, though no CVE was cited for H2O.

oss-sec: Re: HTTP/2 Bomb affects Apache httpd, nginx, envoy, & pingora
The operational view lives in Mallory

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t — which of your assets are affected, which threat actors are using it right now, which detections to deploy, and what to do next.
Exposure mapping

Map indicators from this story to your assets and identify affected systems in minutes.

Threat actor evidence

Every observed campaign, victim, and pivot linked to actors named in this story.

Associated malware

Malware, exploits, and IOCs connected to the activity described here.

Detection signatures

YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.

Scheduled alerts

Get matching new stories delivered to your team as they break — not the next morning.

AI threads

Ask questions about this story and take action on the answers.

HTTP/2 Bomb DoS Flaw Hits Apache, nginx, IIS, Envoy, and Pingora | Mallory