CVE-2024-27919

HIGHNVD 7.59.0▲
EchelonGraph scoreHIGH confidence

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

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 87%
CISA-KEV: Not listedEPSS: 87%CVSS: 7.5Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceeded. This allows an attacker to send an sequence of CONTINUATION frames without the END_HEADERS bit set causing unlimited memory consumption. This can lead to denial of service through memory exhaustion. Users should upgrade to versions 1.29.2 to mitigate the effects of the CONTINUATION flood. Note that this vulnerability is a regression in Envoy version 1.29.0 and 1.29.1 only. As a workaround, downgrade to version 1.28.1 or earlier or disable HTTP/2 protocol for downstream connections.

CVSS v3
7.5
EG Score
9.0(high)
EG Risk
90(Track)
EG Risk 90/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
Severity90% × 45%
Exploitation87% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.7%
KEV
Not listed

Published

April 4, 2024

Last Modified

November 4, 2025

References (9)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 24× 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-23 02:35 UTCEG score recompute
  2. 2026-07-22 21:22 UTCEG score recompute▲ 1.50
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-19 14:30 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-15 16:56 UTCEPSS rescore
  8. 2026-07-15 16:56 UTCEPSS rescore
  9. 2026-07-14 14:55 UTCOSV refresh
  10. 2026-07-13 06:11 UTCEPSS rescore
  11. 2026-07-12 05:45 UTCEPSS rescore
  12. 2026-07-07 13:45 UTCEPSS rescore
  13. 2026-07-07 13:45 UTCEPSS rescore
  14. 2026-07-06 16:26 UTCEPSS rescore
  15. 2026-07-06 16:26 UTCEPSS rescore
  16. 2026-07-05 02:29 UTCEPSS rescore
  17. 2026-07-01 15:05 UTCEPSS rescore
  18. 2026-06-27 03:07 UTCEPSS rescore
  19. 2026-06-27 03:07 UTCEPSS rescore
  20. 2026-06-26 15:39 UTCOSV refresh
  21. 2026-06-24 14:04 UTCEPSS rescore
  22. 2026-06-24 14:04 UTCEPSS rescore
  23. 2026-06-23 21:32 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-16 17:52 UTCEPSS rescore
Show 36 more
  1. 2026-06-16 17:51 UTCEPSS rescore
  2. 2026-06-15 17:47 UTCEPSS rescore
  3. 2026-06-14 23:16 UTCEPSS rescore
  4. 2026-06-13 22:59 UTCEPSS rescore
  5. 2026-06-13 22:59 UTCEPSS rescore
  6. 2026-06-12 23:11 UTCEPSS rescore
  7. 2026-06-12 23:11 UTCEPSS rescore
  8. 2026-06-11 13:59 UTCEPSS rescore
  9. 2026-06-10 22:17 UTCEPSS rescore
  10. 2026-06-10 13:21 UTCEPSS rescore
  11. 2026-06-10 13:21 UTCEPSS rescore
  12. 2026-06-08 22:07 UTCOSV refresh
  13. 2026-06-06 13:46 UTCEPSS rescore
  14. 2026-06-06 13:46 UTCEPSS rescore
  15. 2026-06-05 22:46 UTCEPSS rescore
  16. 2026-06-05 22:46 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-04 13:11 UTCEPSS rescore
  19. 2026-06-04 13:11 UTCEPSS rescore
  20. 2026-06-02 20:12 UTCEPSS rescore
  21. 2026-06-02 20:12 UTCEPSS rescore
  22. 2026-06-01 13:51 UTCEPSS rescore
  23. 2026-06-01 13:51 UTCEPSS rescore
  24. 2026-06-01 13:51 UTCEPSS rescore
  25. 2026-05-31 00:15 UTCEPSS rescore
  26. 2026-05-31 00:15 UTCEPSS rescore
  27. 2026-05-29 13:43 UTCEPSS rescore
  28. 2026-05-29 13:43 UTCEPSS rescore
  29. 2026-05-28 13:44 UTCEPSS rescore
  30. 2026-05-28 13:44 UTCEPSS rescore
  31. 2026-05-28 13:44 UTCEPSS rescore
  32. 2026-05-27 13:40 UTCEPSS rescore
  33. 2026-05-27 13:40 UTCEPSS rescore
  34. 2026-05-26 13:43 UTCEPSS rescore
  35. 2026-05-26 13:43 UTCEPSS rescore
  36. 2026-05-24 05:12 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2024-27919?
CVE-2024-27919 is a high vulnerability published on April 4, 2024. Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceeded. This allows an attacker to send an…
When was CVE-2024-27919 disclosed?
CVE-2024-27919 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-27919 actively exploited?
CVE-2024-27919 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-27919?
CVE-2024-27919 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-27919?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-27919, 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-27919

Explore →

Is Your Infrastructure Affected by CVE-2024-27919?

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

Start Free Scan →Browse All CVEs