Skip to main content
No exploitation reportedFix available

CVE-2019-15226

No exploitation reported by the sources we read.

  • Published2019-10-09
  • WeaknessCWE-400

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

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.

Timeline

dates in UTC
  1. 2019-10-0916:15CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2019-15226?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2019-15226?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Envoy
BranchAffectedFixed in
1.0= 1.0.0no fix published
1.1= 1.1.0no fix published
1.2= 1.2.0no fix published
1.3= 1.3.0no fix published
1.4= 1.4.0no fix published
1.5= 1.5.0no fix published
1.6= 1.6.0no fix published
1.7= 1.7.0no fix published
1.7= 1.7.1no fix published
1.8= 1.8.0no fix published
1.9= 1.9.0no fix published
1.9= 1.9.1no fix published

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.17.5read 2026-10-23
  • NVDCVSS 2.07.8read 2026-10-23
  • NVDweakness (CWE)CWE-400read 2026-10-23
  • FIRST EPSSEPSS score64.5 %read 2026-10-23

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2019-10-09
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2019-15226?

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.

Is CVE-2019-15226 actively exploited?

Active exploitation of CVE-2019-15226 has not been confirmed. Its EPSS score was 64.5% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2019-15226?

CVE-2019-15226 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month