CVE-2026-48913

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

Score 7.3 from GitHub Security Advisory (severity: HIGH) published 2026-06-08. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — Patch released this week
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.3Exploit: None knownExposed: 0

A fix is available — apply it.

Use After Free vulnerability in Apache HTTP Server module mod_http2 when file handles are already exhausted.

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

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

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
Severity73% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
40%
KEV
Not listed

Published

June 8, 2026

Last Modified

July 23, 2026

Advisory Details (2)

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

oss-security - CVE-2026-48913: Apache HTTP Server: mod_http2 memory corruption when file handles exhausted

http://www.openwall.com/lists/oss-security/2026/06/08/15
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-48913(7)

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

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibapache2-mod-proxy-uwsgi (2.4.58-1ubuntu8.15) @ noble2026-08-20ubuntu
ubuntuapache2-utils (2.4.18-2ubuntu3.17+esm19) @ xenial2026-08-20ubuntu
redhatmod_http2-0:2.0.26-2.el9_4.32026-08-18redhat
redhatmod_http2-0:2.0.29-2.el10_0.22026-08-05redhat
redhatmod_http2-0:2.0.26-4.el9_6.22026-08-05redhat
redhatmod_http2-0:2.0.29-4.el10_2.22026-07-01redhat
redhathttpd-main-2.4.68-1.hum12026-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

(8 across 8 ecosystems)
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.68-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.68-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.68-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.68-r0—
Debian:11(1)
PackageVulnerable rangeFixed inDependents
apache22.4.48-3.1 ... 2.4.67-1~deb11u2 (84 versions)2.4.67-1~deb11u3—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache22.4.57-2 ... 2.4.67-2 (53 versions)2.4.68-1~deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache22.4.65-2 ... 2.4.68-1~deb12u1 (27 versions)2.4.68-1~deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache22.4.65-2 ... 2.4.68-1~deb13u1 (28 versions)2.4.68-1—

Weakness Classification(1)

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

Additional Vendor Advisories

(2)

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 30× in last 7d / 131× 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 256 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48913?
CVE-2026-48913 is a high vulnerability published on June 8, 2026. Use After Free vulnerability in Apache HTTP Server module mod_http2 when file handles are already exhausted. This issue affects Apache HTTP Server: from 2.4.55 through 2.4.67.
When was CVE-2026-48913 disclosed?
CVE-2026-48913 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48913 actively exploited?
CVE-2026-48913 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.5% of all scored CVEs.
What is the CVSS score of CVE-2026-48913?
CVE-2026-48913 has a CVSS v3.1 base score of 7.3 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-48913?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48913, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-48913?

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

Start Free Scan →Browse All CVEs