CVE-2024-27316

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 88% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • 777 internet-exposed hosts are running an affected version right now
  • High exploitation likelihood — EPSS 91%
CISA-KEV: Not listedEPSS: 91%CVSS: 7.5Exploit: NoneExposed: 777

A fix is available — apply it.

HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.

Live · internet exposure

777 internet-exposed hosts are running an affected version of CVE-2024-27316 right now.

across 61 countries (United States, Germany, Japan, France, Netherlands)top: http_server
See the live KEV-Exposure radar →Found passively from public internet-scan data — aggregate, host-redacted.

EchelonGraph is the only CVE feed that fuses live vulnerability intelligence with its own live internet-exposure radar — so you see not just that a CVE is exploited, but how much of the internet is exposed to it right now.

CVSS v3
7.5
EG Score
9.0(high)
EPSS
99.8%
KEV
Not listed

Published

April 4, 2024

Last Modified

November 4, 2025

References (15)

Vendor Advisories for CVE-2024-27316(17)

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 / EcosystemFixed in / PatchReleasedSource
ubuntuapache2-utils (2.4.18-2ubuntu3.17+esm12) @ xenial2026-05-24ubuntu
ubuntulibapache2-mod-proxy-uwsgi (2.4.58-1ubuntu8.1) @ noble2026-05-24ubuntu
ubuntulibapache2-mod-proxy-uwsgi (2.4.57-2ubuntu2.4) @ mantic2026-05-24ubuntu
redhateap7-wildfly-0:7.3.15-5.GA_redhat_00003.1.el7eap2025-09-25redhat
redhateap7-wildfly-0:7.1.12-2.GA_redhat_00002.1.ep7.el72025-09-25redhat
redhatHTTP-22024-08-08redhat
redhateap7-wildfly-0:7.4.18-1.GA_redhat_00001.1.el8eap2024-08-08redhat
redhateap7-wildfly-0:7.4.18-1.GA_redhat_00001.1.el9eap2024-08-08redhat
redhateap7-wildfly-0:7.4.18-1.GA_redhat_00001.1.el7eap2024-08-08redhat
redhateap8-wildfly-0:8.0.2-5.GA_redhat_00012.1.el9eap2024-07-08redhat
redhatmod_http2-0:1.15.19-3.el9_0.62024-05-28redhat
redhatmod_http2-0:1.15.19-4.el9_2.62024-05-28redhat
redhathttpd:2.4-8060020240422183714.ad008a3a2024-05-20redhat
redhathttpd:2.4-8080020240502175002.63b345852024-05-16redhat
redhatjbcs-httpd24-httpd2024-05-07redhat
redhatjbcs-httpd24-nghttp2-0:1.43.0-13.el7jbcs2024-05-07redhat
redhatmod_http2-0:2.0.26-2.el9_42024-04-30redhat
redhatmod_http2-0:1.15.19-5.el9_3.12024-04-18redhat
redhathttpd:2.4-8090020240405093943.a75119d52024-04-11redhat

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(2)

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

Additional Vendor Advisories

(4)

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 1× in last 7d / 9× 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.

  1. 2026-07-22 14:07 UTCEPSS rescore
  2. 2026-07-14 14:55 UTCOSV refresh
  3. 2026-07-11 08:26 UTCEPSS rescore
  4. 2026-07-01 15:05 UTCEPSS rescore
  5. 2026-06-26 15:39 UTCOSV refresh
  6. 2026-06-25 13:48 UTCEPSS rescore
  7. 2026-06-25 13:48 UTCEPSS rescore
  8. 2026-06-23 21:32 UTCEPSS rescore
  9. 2026-06-23 21:32 UTCEPSS rescore
  10. 2026-06-15 17:47 UTCEPSS rescore
  11. 2026-06-12 23:11 UTCEPSS rescore
  12. 2026-06-10 22:17 UTCEPSS rescore
  13. 2026-06-10 13:21 UTCEPSS rescore
  14. 2026-06-10 13:21 UTCEPSS rescore
  15. 2026-06-08 22:07 UTCOSV refresh
  16. 2026-06-08 14:16 UTCEPSS rescore
  17. 2026-06-08 14:16 UTCEPSS rescore
  18. 2026-06-07 15:24 UTCEPSS rescore
  19. 2026-06-07 15:24 UTCEPSS rescore
  20. 2026-06-05 22:46 UTCEPSS rescore
  21. 2026-06-05 22:46 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
Show 15 more
  1. 2026-06-04 13:11 UTCEPSS rescore
  2. 2026-05-31 22:30 UTCEPSS rescore
  3. 2026-05-31 22:30 UTCEPSS rescore
  4. 2026-05-29 13:43 UTCEPSS rescore
  5. 2026-05-29 13:43 UTCEPSS rescore
  6. 2026-05-28 13:44 UTCEPSS rescore
  7. 2026-05-28 13:44 UTCEPSS rescore
  8. 2026-05-28 13:44 UTCEPSS rescore
  9. 2026-05-26 13:43 UTCEPSS rescore
  10. 2026-05-26 13:43 UTCEPSS rescore
  11. 2026-05-26 07:18 UTCEPSS rescore
  12. 2026-05-26 07:18 UTCEPSS rescore
  13. 2026-05-24 05:10 UTCEG score recompute
  14. 2026-05-24 05:10 UTCVendor advisory
  15. 2026-05-24 05:10 UTCGHSA enrichment

Publicly available exploits

(2 references)

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

  • GitHub PoCaeyesec/CVE-2024-27316_poc
    First seen Apr 17, 2024
    Open source ↗
  • GitHub PoClockness-Ko/CVE-2024-27316
    First seen Apr 9, 2024

    Proof of concept (PoC) for CVE-2024-27316 (tested), CVE-2024-30255 (untested), CVE-2024-31309 (untested), CVE-2024-28182 (untested), CVE-2024-2653 (untested) and CVE-2024-27919 (untested)

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2024-27316?
CVE-2024-27316 is a high vulnerability published on April 4, 2024. HTTP/2 incoming headers exceeding the limit are temporarily buffered in nghttp2 in order to generate an informative HTTP 413 response. If a client does not stop sending headers, this leads to memory exhaustion.
When was CVE-2024-27316 disclosed?
CVE-2024-27316 was first published in the National Vulnerability Database on April 4, 2024, with the most recent update on November 4, 2025. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-27316 actively exploited?
CVE-2024-27316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-27316?
CVE-2024-27316 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2024-27316?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-27316, 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-2024-27316

Explore →

Is Your Infrastructure Affected by CVE-2024-27316?

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

Start Free Scan →Browse All CVEs