Log in Start free

Vulnerability · Published Mar 10, 2026 · Assigned by GitHub_M

CVE-2026-26330Envoy global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly

Medium 5.3

In plain English

A medium-severity use-after-free in envoy from envoyproxy. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.4% (higher than 29% of all known vulnerabilities).

Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.4%top 70.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

Official description

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Gogithub.com/envoyproxy/envoyno fix listedGHSA-c23c-rp3m-vpg3
Gogithub.com/envoyproxy/envoyno fix listedGHSA-c23c-rp3m-vpg3

Affected products (as reported)

VendorProductVersions
envoyproxy envoy >= 1.37.0, < 1.37.1>= 1.36.0, < 1.36.5>= 1.35.0, < 1.35.9< 1.34.13

Weakness: CWE-416 · Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H

References