All vulnerabilities

Servers and applications

CVE-2026-26330

global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly

Severity
High 7.5
Published
10 Mar 2026
Last changed
17 Jun 2026
Added to UpHeron
1 Nov 2026
Fixed in
1.34.13, 1.35.8, 1.36.5
Exploit chance
0.4% in the next 30 daysHigher than 29% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Use after free (CWE-416)
Attack
Over the network · No login needed · No user action needed
Attacker can
Take it down
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Also known as
GHSA-c23c-rp3m-vpg3
Sources
NVD, Project advisories (GitHub)

Description

At the rate limit filter, if we enabled the response phase limit with apply_on_stream_done in the rate limit configuration 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 we send the second limit request at response phase, and the second limit request fails directly, we may access the previous request's inner state and result in crash.

This only happens when both the request phase limit and response phase limit are enabled in the rate limit filter, and requires the request to rate limit service fails directly (For example, if from Envoy's perspective, no healthy endpoint for rate limit service may result the request fails directly).

From envoyproxy/envoy's security advisory. Shortened; the full text is there.

Workarounds

This could be worked around by splitting the rate limit filter. That is, if there is a rate limit filter that contains normal rate limit configuration (request phase limit, without apply_on_stream_done) and also rate limit configuration with apply_on_stream_done (response phase limit). Splitting them into two rate limit filters and ensure one filter only contains normal rate limit configuration (without apply_on_stream_done), and one only contains rate limit configuration with apply_on_stream_done could avoid this problem.

Workarounds as given by envoyproxy/envoy's security advisory.

Affected software

SoftwareAffected versions
EnvoyServers and applications · cpe:a:envoyproxy:envoy
  • Every version before 1.34.13
  • From 1.35.0 before 1.35.8
  • From 1.36.0 before 1.36.5
  • Version 1.37.0
EnvoyServers and applications · github:envoyproxy/envoy
  • From 1.36.0 before 1.36.5

About Envoy

service proxy

From Wikidata, CC0 1.0.
Docker Hub pulls
5,809,928,938Docker Hub, 15 Nov 2026
GitHub stars
29,237GitHub, 15 Nov 2026
Forks
5,728GitHub, 15 Nov 2026
Latest release
v1.40.2GitHub, 15 Nov 2026
Released
27 Oct 2026GitHub
Developer
Alyssa WilkWikidata
License
Apache Software License 2.0Wikidata
Written in
C++Wikidata
First released
8 Aug 2016Wikidata
First published on GitHub
8 Aug 2016GitHub

Release lines

ReleaseLatestSecurity fixes
1.401.40.2Until 13 Oct 2027
1.391.39.6Until 14 Jul 2027
1.381.38.9Until 23 Apr 2027
1.371.37.11Until 13 Jan 2027
1.361.36.13Ended 14 Oct 2026
1.351.35.13Ended 23 Jul 2026

From endoflife.date.

References

  • NVD https://nvd.nist.gov/vuln/detail/CVE-2026-26330
  • CVE.org https://www.cve.org/CVERecord?id=CVE-2026-26330
  • GitHub Advisory Database https://github.com/advisories/GHSA-c23c-rp3m-vpg3
  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-c23c-rp3m-vpg3