CVE-2024-27316

CRITICALNVD 7.59.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because EPSS predicted 91% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this weekElevated
9.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • 916 internet-facing services (distinct ip:port) on record running an affected version — derived from Shodan data (© Shodan); a patched service can stay counted while its port stays open
  • High exploitation likelihood — EPSS 91%
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 91%CVSS: 7.5Exploit: Public PoCExposed services: 916

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.

Internet exposure · derived from Shodan data

916 internet-facing services (distinct ip:port) on record running a version that maps to CVE-2024-27316, in our KEV-Exposure radar’s Shodan-derived sample.

across 73 countries (United States, Germany, Japan, Netherlands, France)top: http_server
See the KEV-Exposure radar →Derived from Shodan data. Shodan data is owned by Shodan, which holds its copyright (© Shodan). EchelonGraph claims no ownership of it or copyright in it. Aggregate, host-redacted.

How it counts: every 12 hours, when Shodan query credits allow, the radar runs one Shodan query per tracked product, reads up to 100 ip:port services per query, and keeps a service when its banner version matches a CISA-KEV or high-EPSS CVE; a service is dropped when neither a search nor a Shodan InternetDB port re-check has refreshed it for 21 days. A re-check that finds the port still listed by Shodan InternetDB refreshes the service without re-reading the banner, so a patched service can stay counted while its port stays open. A count is a banner-version inference over a sample, not an exploit test and not an internet-wide census, and the unit is a service, not a machine: a machine answering on two ports counts twice.

CVSS v3
7.5
EG Score
9.0CRITICALhigh confidence
EG Risk
85
EG Risk 85/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity75% × 45%
Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation91% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
91%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.0): severity, escalated by confirmed exploitation. This CVE's 9.0 is EPSS's lift toward 9.0 from its impact severity (EG Severity, CVSS 7.5 HIGH): a likelihood of exploitation, not impact.

EG Severity
7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
91% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-23). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 4, 2024

Last Modified

November 4, 2025

Advisory Details (7)

Auto-updated Oct 12, 2026
Patch available.
Web page

[SECURITY] Fedora 38 Update: mod_http2-2.0.27-1.fc38 - package-announce - Fedora mailing-lists

https://lists.fedoraproject.org/archives/list/[email protected]/message/FO73U3SLBYFGIW2YKXOK7RI4D6DJSZ2B/
Web pageMentions a patch (unverified)

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

https://lists.debian.org/debian-lts-announce/2024/05/msg00013.html
Web pageMentions a patch (unverified)

Apache HTTP Server 2.4 vulnerabilities - The Apache HTTP Server Project

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

oss-security - CVE-2024-27316: Apache HTTP Server: HTTP/2 DoS by memory exhaustion on endless continuation frames

http://www.openwall.com/lists/oss-security/2024/04/04/4
Web page

Full Disclosure: APPLE-SA-07-29-2024-4 macOS Sonoma 14.6

http://seclists.org/fulldisclosure/2024/Jul/18
Web page

oss-security - CERT/CC VU#421644: HTTP/2 CONTINUATION frames can be utilized for DoS attacks

https://www.openwall.com/lists/oss-security/2024/04/03/16
Web page

About the security content of macOS Sonoma 14.6 - Apple Support

https://support.apple.com/kb/HT214119

Patch Availability(20)

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

(14 across 14 ecosystems)
Alpine:v3.16(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.17(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.18(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.19(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-r0: fixed in 2.4.59-r0
—
Debian:10(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.38-3 ... 2.4.58-1 (78 versions)
  • every version up to 2.4.59-1~deb10u1: fixed in 2.4.59-1~deb10u1
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.48-3.1 ... 2.4.59-1~deb10u1 (44 versions)
  • every version up to 2.4.59-1~deb11u1: fixed in 2.4.59-1~deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache22.4.57-2, 2.4.57-3, 2.4.58-1, 2.4.59-1~deb10u1, 2.4.59-1~deb11u1
  • every version up to 2.4.59-1~deb12u1: fixed in 2.4.59-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-1: fixed in 2.4.59-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache2—
  • every version up to 2.4.59-1: fixed in 2.4.59-1
—

Weakness Classification(2)

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

Additional Vendor Advisories

(3)

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 27× in last 7d / 50× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 91 of 104 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 9 repeat rows among the latest 100 are merged into the row they repeat. The 13 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-23 21:03 UTCEG score recompute
  2. 2026-10-23 21:03 UTCVendor advisory
  3. 2026-10-23 21:03 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  4. 2026-10-22 21:38 UTCEG score recompute
  5. 2026-10-22 21:38 UTCVendor advisory
  6. 2026-10-22 21:38 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  7. 2026-10-22 16:31 UTCEPSS rescoreEPSS 91% · 99th percentile
  8. 2026-10-21 22:12 UTCEG score recompute
  9. 2026-10-21 22:12 UTCVendor advisory
  10. 2026-10-21 22:11 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  11. 2026-10-20 22:47 UTCEG score recompute
  12. 2026-10-20 22:47 UTCVendor advisory
  13. 2026-10-20 22:47 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  14. 2026-10-20 16:30 UTCEPSS rescoreEPSS 91% · 99th percentile
  15. 2026-10-19 23:03 UTCEG score recompute
  16. 2026-10-19 23:03 UTCVendor advisory
  17. 2026-10-19 23:02 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  18. 2026-10-18 22:27 UTCEG score recompute
  19. 2026-10-18 22:27 UTCVendor advisory
  20. 2026-10-18 22:27 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  21. 2026-10-18 07:21 UTCEG score recompute
  22. 2026-10-17 22:43 UTCEG score recompute
  23. 2026-10-17 22:43 UTCVendor advisory
  24. 2026-10-17 22:42 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  25. 2026-10-16 23:15 UTCEG score recompute
Show 66 more
  1. 2026-10-16 23:15 UTCVendor advisory
  2. 2026-10-16 23:14 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  3. 2026-10-15 20:29 UTCEG score recompute
  4. 2026-10-15 20:29 UTCVendor advisory
  5. 2026-10-15 20:29 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  6. 2026-10-14 16:30 UTCEPSS rescoreEPSS 91% · 99th percentile
  7. 2026-10-14 14:26 UTCEG score recompute
  8. 2026-10-14 14:26 UTCVendor advisory
  9. 2026-10-14 14:25 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  10. 2026-10-13 14:04 UTCEG score recompute
  11. 2026-10-13 14:04 UTCVendor advisory
  12. 2026-10-13 14:04 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  13. 2026-10-12 14:40 UTCEG score recompute
  14. 2026-10-12 14:40 UTCVendor advisory
  15. 2026-10-12 14:39 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  16. 2026-10-12 14:38 UTCGHSA enrichmentGHSA-5qc4-82jh-h385 · GitHub severity HIGH · GitHub CVSS 7.5
  17. 2026-10-11 21:23 UTCEG score recompute
  18. 2026-10-11 16:17 UTCEG score recompute
  19. 2026-10-11 16:06 UTCOSV refresh
  20. 2026-10-05 17:41 UTCEPSS rescoreEPSS 91% · 99th percentile
  21. 2026-09-30 17:00 UTCEG score recompute
  22. 2026-09-30 15:01 UTCEPSS rescoreEPSS 91% · 99th percentile
  23. 2026-09-29 15:17 UTCEPSS rescoreEPSS 91% · 99th percentile
  24. 2026-09-28 13:49 UTCEPSS rescoreEPSS 91% · 99th percentile
  25. 2026-09-24 14:01 UTCEPSS rescoreEPSS 91% · 99th percentile
  26. 2026-09-22 14:46 UTCEPSS rescoreEPSS 91% · 99th percentile
  27. 2026-09-22 03:45 UTCOSV refresh
  28. 2026-09-20 20:14 UTCEPSS rescoreEPSS 91% · 99th percentile
  29. 2026-09-19 15:40 UTCEPSS rescoreEPSS 91% · 99th percentile
  30. 2026-09-12 14:59 UTCEPSS rescoreEPSS 91% · 99th percentile
  31. 2026-09-06 13:46 UTCEPSS rescoreEPSS 91% · 99th percentile
  32. 2026-09-05 15:26 UTCEPSS rescoreEPSS 91% · 99th percentile
  33. 2026-09-03 01:00 UTCOSV refresh
  34. 2026-09-01 13:52 UTCEPSS rescoreEPSS 91% · 99th percentile
  35. 2026-08-30 19:15 UTCEPSS rescoreEPSS 91% · 99th percentile
  36. 2026-08-28 21:39 UTCEPSS rescoreEPSS 91% · 99th percentile
  37. 2026-08-26 14:44 UTCEPSS rescoreEPSS 91% · 99th percentile
  38. 2026-08-20 22:53 UTCEPSS rescoreEPSS 91% · 99th percentile
  39. 2026-08-19 17:02 UTCEPSS rescoreEPSS 91% · 99th percentile
  40. 2026-08-16 13:30 UTCOSV refresh
  41. 2026-08-13 21:58 UTCEPSS rescoreEPSS 91% · 99th percentile
  42. 2026-08-04 10:36 UTCEPSS rescoreEPSS 91% · 99th percentile
  43. 2026-08-01 07:36 UTCOSV refresh
  44. 2026-07-30 01:29 UTCEPSS rescoreEPSS 91% · 99th percentile
  45. 2026-07-27 14:11 UTCEPSS rescoreEPSS 91% · 99th percentile
  46. 2026-07-25 14:16 UTCEPSS rescoreEPSS 91% · 99th percentile
  47. 2026-07-24 14:16 UTCEPSS rescoreEPSS 91% · 99th percentile
  48. 2026-07-23 02:35 UTCEG score recompute
  49. 2026-07-22 14:07 UTCEPSS rescoreEPSS 91% · 99th percentile
  50. 2026-07-14 14:55 UTCOSV refresh
  51. 2026-07-11 08:26 UTCEPSS rescoreEPSS 91% · 99th percentile
  52. 2026-07-01 15:05 UTCEPSS rescoreEPSS 91% · 99th percentile
  53. 2026-06-26 15:39 UTCOSV refresh
  54. 2026-06-25 13:48 UTCEPSS rescoreEPSS 91% · 99th percentile
  55. 2026-06-23 21:32 UTCEPSS rescoreEPSS 91% · 99th percentile
  56. 2026-06-15 17:47 UTCEPSS rescoreEPSS 91% · 99th percentile
  57. 2026-06-12 23:11 UTCEPSS rescoreEPSS 88% · 99th percentile
  58. 2026-06-10 22:17 UTCEPSS rescoreEPSS 88% · 99th percentile
  59. 2026-06-10 13:21 UTCEPSS rescoreEPSS 88% · 99th percentile
  60. 2026-06-08 22:07 UTCOSV refresh
  61. 2026-06-08 14:16 UTCEPSS rescoreEPSS 88% · 99th percentile
  62. 2026-06-07 15:24 UTCEPSS rescoreEPSS 88% · 99th percentile
  63. 2026-06-05 22:46 UTCEPSS rescoreEPSS 88% · 99th percentile
  64. 2026-06-05 06:09 UTCEPSS rescoreEPSS 88% · 99th percentile
  65. 2026-06-04 13:11 UTCEPSS rescoreEPSS 88% · 99th percentile
  66. 2026-05-31 22:30 UTCEPSS rescoreEPSS 88% · 99th percentile

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (2 GitHub PoCs). Defenders should treat patch urgency accordingly.

  • GitHub PoCaeyesec/CVE-2024-27316_poc
    Published Apr 17, 2024
    Open source ↗
  • GitHub PoClockness-Ko/CVE-2024-27316
    Published 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 ↗

Frequently asked(5)

What is CVE-2024-27316?
CVE-2024-27316 is a critical-severity vulnerability; its CVE record was 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 the CVE record for CVE-2024-27316 published?
The CVE record for CVE-2024-27316 was published on April 4, 2024. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 4, 2025; the record at its source may have been updated since.
Is CVE-2024-27316 actively exploited?
CVE-2024-27316 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 91% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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 (CRITICAL).
How do I remediate CVE-2024-27316?
A fix for CVE-2024-27316 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2024-27316 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-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.