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 — 4 sources updated 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
39%
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(4)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.66-2ubuntu2.4) @ resolute2026-07-16ubuntu
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.

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 16× in last 7d / 81× 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 139 total refreshes for this CVE.

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

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 61.4% 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

Explore the affected products and dependency analysis for 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