BIT-envoy-2026-26330

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/envoy/BIT-envoy-2026-26330.json
JSON Data
https://api.test.osv.dev/v1/vulns/BIT-envoy-2026-26330
Aliases
Published
2026-03-12T08:39:47.564Z
Modified
2026-03-12T09:26:08.133875Z
Summary
Envoy global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
Details

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 applyonstream_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.

Database specific
{
    "cpes": [
        "cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:go:*:*"
    ],
    "severity": "High"
}
References

Affected packages

Bitnami / envoy

Package

Name
envoy
Purl
pkg:bitnami/envoy

Severity

  • 7.5 (High) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.34.13
Introduced
1.35.0
Fixed
1.35.9
Introduced
1.36.0
Fixed
1.36.5
Introduced
1.37.0
Fixed
1.37.1

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/envoy/BIT-envoy-2026-26330.json"