CVE-2019-15226

HIGHNVD 7.58.5▲
EchelonGraph scoreHIGH confidence

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

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

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

Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had O(n^2) performance characteristics. A remote attacker may craft a request that stays below the maximum request header size but consists of many thousands of small headers to consume CPU and result in a denial-of-service attack.

CVSS v3
7.5
EG Score
8.5(high)
EG Risk
69(Track)
EG Risk 69/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
Severity85% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.2%
KEV
Not listed

Published

October 9, 2019

Last Modified

November 21, 2024

References (6)

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-15226?
CVE-2019-15226 is a high vulnerability published on October 9, 2019. Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had…
When was CVE-2019-15226 disclosed?
CVE-2019-15226 was first published in the National Vulnerability Database on October 9, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-15226 actively exploited?
CVE-2019-15226 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2019-15226?
CVE-2019-15226 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2019-15226?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-15226, 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-2019-15226

Explore →

Is Your Infrastructure Affected by CVE-2019-15226?

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

Start Free Scan →Browse All CVEs