CVE-2026-23918

HIGHPre-NVD 8.88.9▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: cisa-adp, epss, ghsa
Trending — 4 sources updated this weekElevated
8.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 50%CVSS: 8.8Exploit: Elevated riskExposed: 0

A fix is available — apply it.

Double Free and possible RCE vulnerability in Apache HTTP Server with the HTTP/2 protocol.

This issue affects Apache HTTP Server: 2.4.66.

Users are recommended to upgrade to version 2.4.67, which fixes the issue.

CVSS v3
8.8
EG Score
8.9(high)
EG Risk
60(Track)
EG Risk 60/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
Severity89% × 45%
Exploitation50% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
50%
EPSS %ILE
99%
KEV
Not listed

Published

May 4, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated May 4, 2026
⚠️ Active exploitation confirmed. Patch available.
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-23918(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibapache2-mod-proxy-uwsgi (2.4.52-1ubuntu4.20) @ jammy2026-08-23ubuntu
redhathttpd-main-2.4.67-0.1.hum12026-05-06redhat

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.20(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.67-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.67-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.67-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.67-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
apache2—2.4.67-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
apache22.4.57-2 ... 2.4.67-1~deb12u1 (46 versions)2.4.67-1~deb12u2—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
apache22.4.65-2 ... 2.4.66-1~deb13u1 (6 versions)2.4.66-1~deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
apache22.4.65-2 ... 2.4.66-4 (11 versions)2.4.66-5—

Weakness Classification(2)

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 7× in last 7d / 74× 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 247 total refreshes for this CVE.

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

Publicly available exploits

(6 references)

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

  • Exploit-DBEDB-52577
    First seen May 26, 2026

    Apache HTTP Server 2.4.66 - 'mod_http2' Double-Free Denial of Service

    Open source ↗
  • GitHub PoCstriga-ai/CVE-2026-23918
    First seen May 11, 2026

    Double-free in Apache httpd mod_http2 stream cleanup leading to pre-auth RCE.

    Open source ↗
  • GitHub PoCxeloxa/CVE-2026-23918-Apache-H2-PoC
    First seen May 6, 2026

    Proof-of-Concept exploit for CVE-2026-23918 (Apache mod_http2 double-free). Features multi-mode DoS (Rapid-RST, Slow-Drip) and passive RCE/vulnerability detection for Apache 2.4.66.

    Open source ↗
  • GitHub PoCrhasan-com/CVE-2026-23918
    First seen May 6, 2026

    Apache HTTP/2 double-free vulnerability PoC (CVE-2026-23918)

    Open source ↗
  • GitHub PoCqassam-315/CVE-2026-23918-Elite-Auditor
    First seen May 5, 2026

    Elite reconnaissance script for auditing Apache's HTTP/2 stack against memory corruption (CVE-2026-23918). Features ALPN protocol forcing and monochrome dashboard intelligence. Built for Blue Teams and Security Researchers.

    Open source ↗
  • GitHub PoC12lie20/CVE-2026-23918-test
    First seen May 5, 2026

    This repository contains a Proof of Concept (PoC) demonstrating the Double Free vulnerability (CVE-2026-23918) in Apache HTTP Server 2.4.66 `mod_http2`.

    Open source ↗

Frequently asked(5)

What is CVE-2026-23918?
CVE-2026-23918 is a high vulnerability published on May 4, 2026. Double Free and possible RCE vulnerability in Apache HTTP Server with the HTTP/2 protocol. This issue affects Apache HTTP Server: 2.4.66. Users are recommended to upgrade to version 2.4.67, which fixes the issue.
When was CVE-2026-23918 disclosed?
CVE-2026-23918 was first published in the National Vulnerability Database on May 4, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23918 actively exploited?
CVE-2026-23918 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 50% probability of exploitation in the next 30 days, which ranks it in the top 1.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23918?
CVE-2026-23918 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.9.
How do I remediate CVE-2026-23918?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23918, 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-23918

Explore →

Is Your Infrastructure Affected by CVE-2026-23918?

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

Start Free Scan →Browse All CVEs