envoyproxy · Envoy · published 2026-03-10
CVE-2026-26330Envoy global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
Routine No exploitation evidence; EPSS 0.4%.
CVE-2026-26330 is not known to be exploited in the wild. EPSS estimates a 0.4% chance of exploitation in the next 30 days, higher than 29% of all CVEs. This Envoy vulnerability: CVSS 5.3 (v3.1). Fixed upstream in Envoy 1.37.1, 1.36.5, 1.35.9, 1.35.8 (+1 more). Routine: patch when convenient.
Jump to: Remediation Exploit intelAffected versionsDescription
Remediation#
Fixed upstream in Envoy 1.37.1, 1.36.5, 1.35.9, 1.35.8, 1.34.13.
Patch events
Web serverEnvoy
Envoy security releases: 1.37.1, 1.36.5, 1.35.9, 1.35.8, 1.34.13
Upgrade to
1.37.11.36.51.35.91.35.81.34.13Why: CVE-2026-26311: Public proof-of-concept exists (SSVC exploitation: poc).
Exploit intelligence#
| Signal | Value | Source |
|---|---|---|
| Known exploited | No | CISA KEV |
| Ransomware use | — | CISA KEV |
| EPSS (30-day exploitation probability) | 0.4% (30th pct) | FIRST EPSS v2026.06.15 |
| CVSS base score | 5.3 (v3.1)CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H | CNA / CISA ADP |
| SSVC exploitation | none | CISA Vulnrichment |
| SSVC automatable | No | CISA Vulnrichment |
| SSVC technical impact | partial | CISA Vulnrichment |
Affected versions (from the CVE record)#
- envoyproxy envoy
>= 1.37.0, < 1.37.1(affected)>= 1.36.0, < 1.36.5(affected)>= 1.35.0, < 1.35.9(affected)< 1.34.13(affected)
Description (from the CVE record)#
Envoy is a high-performance edge/middle/service proxy. Prior to 1.37.1, 1.36.5, 1.35.8, and 1.34.13, At the rate limit filter, if the response phase limit with apply_on_stream_done in the rate limit configuration is enabled and the response phase limit request fails directly, it may crash Envoy. When both the request phase limit and response phase limit are enabled, the safe gRPC client instance will be re-used for both the request phase request and response phase request. But after the request phase request is done, the inner state of the request phase limit request in gRPC client is not cleaned up. When a second limit request is sent at response phase, and the second limit request fails directly, the previous request's inner state may be accessed and result in crash. This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.
Quoted from the CVE Program record.