CVE-2026-49975

HIGHPre-NVD 7.57.6▲
EchelonGraph scoreHIGH confidence

Score elevated to 7.6 because EPSS predicts 34% probability of exploitation within the next 30 days (top 1.7% of all CVEs). CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: cisa-adp, epss, ghsa
Elevated
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 4.2%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

Memory Allocation with Excessive Size Value vulnerability in Apache HTTP Server's mod_http leads to denial of service via malicious HTTP requests.

This issue affects Apache HTTP Server: from 2.4.17 through 2.4.67.

CVSS v3
7.5
EG Score
7.6HIGHhigh confidence
EG Risk
65
EG Risk 65/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity76% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
4.2%
EPSS %ILE
90th
KEV
Not listed

Published

June 8, 2026

Last Modified

August 19, 2026

Advisory Details (4)

Auto-updated Jun 10, 2026
⚠️ Active exploitation confirmed. Patch available.
generic Patch Available

[SECURITY] [DLA 4620-1] apache2 security update

https://lists.debian.org/debian-lts-announce/2026/06/msg00009.html
generic

oss-security - CVE-2026-49975: Apache HTTP Server: mod_http2 denial of service

http://www.openwall.com/lists/oss-security/2026/06/08/16
generic Patch Available

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

http://www.openwall.com/lists/oss-security/2026/06/03/3
generic Patch Available🔴 Active Exploitation

Apache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project

https://httpd.apache.org/security/vulnerabilities_24.html

Vendor Advisories for CVE-2026-49975(16)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(19)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntunginx-light (1.28.3-2ubuntu1.3) @ resolute2026-09-14ubuntu
ubuntuapache2-utils (2.4.66-2ubuntu2.2) @ resolute2026-09-14ubuntu
ubuntunginx-light (1.10.3-0ubuntu0.16.04.5+esm9) @ xenial2026-09-14ubuntu
ubuntuapache2-utils (2.4.29-1ubuntu4.27+esm10) @ bionic2026-09-14ubuntu
ubuntunginx-light (1.28.0-6ubuntu1.7) @ questing2026-09-14ubuntu
redhatmod_http2-0:1.15.19-4.el9_2.82026-08-18redhat
redhatmod_http2-0:2.0.26-2.el9_4.32026-08-18redhat
redhatmod_http2-0:2.0.26-4.el9_6.22026-08-05redhat
redhatmod_http2-0:2.0.29-2.el10_0.22026-08-05redhat
redhathttpd:2.4-8060020260702195216.ad008a3a2026-07-08redhat
redhathttpd:2.4-8040020260702193120.522a0ee42026-07-08redhat
redhathttpd:2.4-8080020260702200145.63b345852026-07-07redhat
redhatjbcs-httpd24-mod_http22026-06-22redhat
redhatjbcs-httpd24-mod_http2-0:2.0.29-10.el7jbcs2026-06-22redhat
redhatopenshift-service-mesh/proxyv2-rhel9:17816047242026-06-18redhat
redhatmod_http2-0:2.0.29-4.el10_2.12026-06-11redhat
redhathttpd:2.4-8100020260608081321.489197e62026-06-10redhat
redhathttpd-main-2.4.68-1.hum12026-06-10redhat
redhatmod_http2-0:2.0.26-6.el9_8.12026-06-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(12 across 8 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.68-r0: fixed in 2.4.68-r0
—
nginx—
  • every version up to 1.26.3-r1: fixed in 1.26.3-r1
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.68-r0: fixed in 2.4.68-r0
—
nginx—
  • every version up to 1.28.3-r3: fixed in 1.28.3-r3
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.68-r0: fixed in 2.4.68-r0
—
nginx—
  • every version up to 1.28.3-r3: fixed in 1.28.3-r3
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.68-r0: fixed in 2.4.68-r0
—
nginx—
  • every version up to 1.30.1-r0: fixed in 1.30.1-r0
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.48-3.1 ... 2.4.67-1~deb11u1 (83 versions)
  • every version up to 2.4.67-1~deb11u2: fixed in 2.4.67-1~deb11u2
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.57-2 ... 2.4.67-1~deb12u2 (47 versions)
  • every version up to 2.4.67-1~deb12u3: fixed in 2.4.67-1~deb12u3
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.65-2 ... 2.4.67-1~deb13u2 (23 versions)
  • every version up to 2.4.67-1~deb13u3: fixed in 2.4.67-1~deb13u3
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.65-2 ... 2.4.67-1~deb13u3 (25 versions)
  • every version up to 2.4.67-2: fixed in 2.4.67-2
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(5)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 3× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 362 total refreshes for this CVE.

  1. 2026-10-03 14:25 UTCEPSS rescore
  2. 2026-10-01 19:50 UTCEPSS rescore
  3. 2026-09-30 15:03 UTCEPSS rescore
  4. 2026-09-28 13:51 UTCEPSS rescore
  5. 2026-09-27 13:48 UTCEPSS rescore
  6. 2026-09-26 15:59 UTCEPSS rescore
  7. 2026-09-26 00:27 UTCEPSS rescore
  8. 2026-09-23 17:53 UTCEPSS rescore
  9. 2026-09-18 19:28 UTCEPSS rescore
  10. 2026-09-16 14:08 UTCEPSS rescore
  11. 2026-09-16 05:15 UTCEPSS rescore
  12. 2026-09-14 04:53 UTCEG score recompute▲ 0.10
  13. 2026-09-14 04:53 UTCVendor advisory
  14. 2026-09-14 04:53 UTCGHSA enrichment
  15. 2026-09-13 16:47 UTCEPSS rescore
  16. 2026-09-11 14:53 UTCEPSS rescore
  17. 2026-09-10 09:35 UTCEPSS rescore
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-06 13:47 UTCEPSS rescore
  20. 2026-09-04 05:06 UTCEPSS rescore
  21. 2026-09-02 14:12 UTCEPSS rescore
  22. 2026-09-01 13:54 UTCEPSS rescore
  23. 2026-09-01 04:40 UTCEPSS rescore
  24. 2026-08-31 01:57 UTCEG score recompute
  25. 2026-08-31 01:57 UTCVendor advisory
Show 75 more
  1. 2026-08-31 01:57 UTCGHSA enrichment
  2. 2026-08-30 19:17 UTCEPSS rescore
  3. 2026-08-30 01:22 UTCEPSS rescore
  4. 2026-08-28 21:41 UTCEPSS rescore
  5. 2026-08-26 14:46 UTCEPSS rescore
  6. 2026-08-25 13:49 UTCEPSS rescore
  7. 2026-08-25 01:32 UTCEG score recompute
  8. 2026-08-25 01:32 UTCVendor advisory
  9. 2026-08-25 01:32 UTCGHSA enrichment
  10. 2026-08-23 23:46 UTCVendor advisory
  11. 2026-08-23 23:46 UTCGHSA enrichment
  12. 2026-08-23 11:52 UTCEG score recompute
  13. 2026-08-23 11:52 UTCVendor advisory
  14. 2026-08-23 11:52 UTCGHSA enrichment
  15. 2026-08-23 00:19 UTCEPSS rescore
  16. 2026-08-21 23:49 UTCEPSS rescore
  17. 2026-08-21 19:55 UTCVendor advisory
  18. 2026-08-21 19:55 UTCGHSA enrichment
  19. 2026-08-21 08:21 UTCEG score recompute
  20. 2026-08-21 08:21 UTCVendor advisory
  21. 2026-08-21 08:21 UTCGHSA enrichment
  22. 2026-08-20 22:55 UTCEPSS rescore
  23. 2026-08-20 20:54 UTCVendor advisory
  24. 2026-08-20 20:54 UTCGHSA enrichment
  25. 2026-08-20 09:31 UTCEG score recompute
  26. 2026-08-20 09:31 UTCVendor advisory
  27. 2026-08-20 09:31 UTCGHSA enrichment
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-19 12:26 UTCVendor advisory
  30. 2026-08-19 12:26 UTCGHSA enrichment
  31. 2026-08-19 12:10 UTCEG score recompute
  32. 2026-08-19 12:10 UTCVendor advisory
  33. 2026-08-19 12:09 UTCGHSA enrichment
  34. 2026-08-18 13:48 UTCEPSS rescore
  35. 2026-08-18 12:38 UTCVendor advisory
  36. 2026-08-18 12:38 UTCGHSA enrichment
  37. 2026-08-18 12:15 UTCEG score recompute
  38. 2026-08-18 12:15 UTCVendor advisory
  39. 2026-08-18 12:15 UTCGHSA enrichment
  40. 2026-08-17 13:47 UTCEPSS rescore
  41. 2026-08-17 13:02 UTCVendor advisory
  42. 2026-08-17 13:02 UTCGHSA enrichment
  43. 2026-08-17 01:56 UTCEG score recompute
  44. 2026-08-17 01:56 UTCVendor advisory
  45. 2026-08-17 01:56 UTCGHSA enrichment
  46. 2026-08-16 14:56 UTCEPSS rescore
  47. 2026-08-16 12:21 UTCEG score recompute
  48. 2026-08-16 12:21 UTCVendor advisory
  49. 2026-08-16 12:21 UTCGHSA enrichment
  50. 2026-08-16 02:14 UTCEPSS rescore
  51. 2026-08-16 01:15 UTCVendor advisory
  52. 2026-08-16 01:15 UTCGHSA enrichment
  53. 2026-08-15 12:00 UTCEG score recompute
  54. 2026-08-15 12:00 UTCVendor advisory
  55. 2026-08-15 12:00 UTCGHSA enrichment
  56. 2026-08-15 01:30 UTCEPSS rescore
  57. 2026-08-14 20:41 UTCVendor advisory
  58. 2026-08-14 20:41 UTCGHSA enrichment
  59. 2026-08-14 09:35 UTCVendor advisory
  60. 2026-08-14 09:35 UTCGHSA enrichment
  61. 2026-08-13 22:28 UTCEG score recompute
  62. 2026-08-13 22:28 UTCVendor advisory
  63. 2026-08-13 22:28 UTCGHSA enrichment
  64. 2026-08-13 22:00 UTCEPSS rescore
  65. 2026-08-13 06:20 UTCVendor advisory
  66. 2026-08-13 06:20 UTCGHSA enrichment
  67. 2026-08-12 19:13 UTCEG score recompute
  68. 2026-08-12 19:13 UTCVendor advisory
  69. 2026-08-12 19:13 UTCGHSA enrichment
  70. 2026-08-12 13:51 UTCEPSS rescore
  71. 2026-08-12 08:07 UTCVendor advisory
  72. 2026-08-12 08:06 UTCGHSA enrichment
  73. 2026-08-11 19:40 UTCEG score recompute
  74. 2026-08-11 19:40 UTCVendor advisory
  75. 2026-08-11 19:40 UTCGHSA enrichment

Publicly available exploits

(10 references)

Working exploit code is in the public domain (10 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCnaheeju/POC-CVE-2026-49975
    First seen Sep 16, 2026

    Security research PoC for CVE-2026-49975: HTTP/2 HPACK compression bomb + flow-control hold DoS in Apache mod_http2

    Open source ↗
  • GitHub PoCadminlove520/http2-bomb-detector
    First seen Jun 13, 2026

    HTTP/2 Bomb (CVE-2026-49975) non-destructive vulnerability detector for Nginx / Apache httpd. Zero-dependency Python.

    Open source ↗
  • GitHub PoCmindcodings/http2-bomb-detector
    First seen Jun 13, 2026

    HTTP/2 Bomb (CVE-2026-49975) non-destructive vulnerability detector for Nginx / Apache httpd. Zero-dependency Python.

    Open source ↗
  • GitHub PoCrazureink/cve-2026-49975-http2bomb_reproduction
    First seen Jun 13, 2026
    Open source ↗
  • GitHub PoCEQSTLab/CVE-2026-49975
    First seen Jun 10, 2026

    HTTP2-Bomb

    Open source ↗
  • GitHub PoCLiaoZiqi-GZFLS/CVE-2026-49975
    First seen Jun 10, 2026

    CVE-2026-49975

    Open source ↗
  • GitHub PoCLSG-PolarBear/CVE-2026-49975
    First seen Jun 10, 2026

    CVE-2026-49975漏洞复现

    Open source ↗
  • GitHub PoCrenzi25031469/CVE-2026-49975-HTTP-2-Bomb
    First seen Jun 8, 2026

    Disclosed on June 3, 2026, the "HTTP/2 Bomb" is an unauthenticated remote DoS that combines an HPACK compression bomb with a Slowloris-style hold to exhaust server memory. It affects default HTTP/2 configurations of **nginx, Apache httpd, Microsoft IIS, Envoy, and Cloudflare Pingora**.

    Open source ↗
  • GitHub PoCobrige/http2-bomb
    First seen Jun 5, 2026

    CVE-2026-49975 HTTP/2 Stream Amplification — Docker PoC with Web Console

    Open source ↗
  • GitHub PoCmrx-arafat/CVE-2026-49975-POC
    First seen Jun 4, 2026

    HTTP/2 Bomb PoC — CVE-2026-49975 (HPACK indexed reference bomb + flow-control stall)

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-49975?
CVE-2026-49975 is a high vulnerability published on June 8, 2026. Memory Allocation with Excessive Size Value vulnerability in Apache HTTP Server's mod_http leads to denial of service via malicious HTTP requests. This issue affects Apache HTTP Server: from 2.4.17 through 2.4.67.
When was CVE-2026-49975 disclosed?
CVE-2026-49975 was first published on June 8, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49975 actively exploited?
CVE-2026-49975 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.2% probability of exploitation in the next 30 days (90th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-49975?
CVE-2026-49975 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.6 (HIGH).
How do I remediate CVE-2026-49975?
A fix for CVE-2026-49975 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-49975 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49975

Explore →

Is Your Infrastructure Affected by CVE-2026-49975?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs