CVE-2026-26330 json
Envoy global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
published 2026-03-10 8 mo ago modified 2026-09-08 2 mo ago also BIT-envoy-2026-26330 , EUVD-2026-10806 , GHSA-c23c-rp3m-vpg3
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 29%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami envoy 1.34.13, 1.35.9, 1.36.5, 1.37.1
- envoyproxy envoy 1.34.13, 1.35.9, 1.36.5, 1.37.1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.36% chance of exploitation in the next 30 days, higher than 29% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| OSV | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/envoyproxy/envoy | 1 listed version >=1.36.0, <=1.36.4 |
no fix listed |
| bitnami | envoy | <1.34.13 >=1.35.0, <1.35.9 >=1.36.0, <1.36.5 >=1.37.0, <1.37.1 |
1.34.13 1.35.9 1.36.5 1.37.1 |
Affected products
- envoyproxy envoy
Classification
- Weakness
-
- CWE-416 Use After Free
References
-
github.com
/envoyproxy/envoy/security/advisories/GHSA-c23c-rp3m-vpg3
web, mitigation, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2026-26330
advisory, web
-
github.com
/envoyproxy/envoy
package
Sources
- CVE List CVE-2026-26330
- GitHub Advisory GHSA-c23c-rp3m-vpg3
- NVD CVE-2026-26330
- OSV BIT-envoy-2026-26330
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.