CVE-2026-49975: HTTP/2 Bomb in Apache HTTP Server
- Vendors
- Apache Software FoundationDebian ProjectF5
CVE-2026-49975 is an excessive memory allocation vulnerability in the HTTP/2 implementation of Apache HTTP Server, affecting upstream versions 2.4.17 through 2.4.67. Incorrect cookie-header accounting permits malicious HTTP requests to cause excessive resource consumption. The vulnerability involves compression-bomb and Slowloris-style denial-of-service attacks against mod_http2. Remote exploitation requires neither authentication nor user interaction.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation can exhaust available memory and other server resources, degrading or preventing service to legitimate clients. Availability impact is rated high, with complete availability loss represented in the CVSS v2 assessment. No confidentiality or integrity impact is identified for this vulnerability; arbitrary code execution and privilege escalation are not established consequences.
Mitigation
If you can’t patch tonight, do this now.
For applicable Fortinet deployments, deploy the HTTP/2 Bomb virtual patch supplied in FMWP database update 26.082. No general temporary workaround is specified for this vulnerability in the Apache or Debian remediation information.
Remediation
Patch, then assume compromise.
Upgrade Apache HTTP Server to 2.4.68 or a later supported release containing the fix, or install the applicable distribution security backport. Debian fixes are available in apache2 2.4.67-1~deb12u3 for bookworm and 2.4.67-1~deb13u3 for trixie. For distributions packaging HTTP/2 separately, update mod_http2 using the relevant vendor advisory. Vendor backports may retain an otherwise affected upstream version number, so verify package security status rather than relying solely on that number. Products embedding Apache HTTP Server require their product-specific fixed releases.
Exploits
9 exploits validated by Mallory's analysis. Hidden: 5 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-49975 exploited in the wild?
- As of Nov 17, 2026, Mallory has no reports of CVE-2026-49975 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-49975?
- Yes. Mallory tracks 9 public exploits or proofs of concept for CVE-2026-49975, the earliest disclosed Jun 3, 2026.
- Is there a patch for CVE-2026-49975?
- Upgrade Apache HTTP Server to 2.4.68 or a later supported release containing the fix, or install the applicable distribution security backport. Debian fixes are available in apache2 2.4.67-1~deb12u3 for bookworm and 2.4.67-1~deb13u3 for trixie.
- What products are affected by CVE-2026-49975?
- Apache Software Foundation Apache HTTP Server, Debian Project Debian Linux, and F5 Nginx.
- How severe is CVE-2026-49975?
- CVE-2026-49975 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 33.0% (98th percentile) as of Nov 17, 2026.
Recent activity
133 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.