Skip to main content
VulnerabilityPublished

CVE-2026-26311: envoyproxy envoy · Use After Free

Affects envoyproxy envoySource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium · fixed in 1.37.1 : update envoyproxy envoy when convenient.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 29% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.37.1, 1.36.5, 1.35.9 +1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

What to do

Upgrade envoy to 1.37.1, 1.36.5, 1.35.9 or 1.34.13; envoyproxy/envoy to 1.34.13.

Affected software

ProductAffectedFixed in
envoyproxyenvoyAffected
  • >=1.37.0 <1.37.1
Fixed in
  • 1.37.1
envoyproxyenvoyAffected
  • >=1.36.0 <1.36.5
Fixed in
  • 1.36.5
envoyproxyenvoyAffected
  • >=1.35.0 <1.35.9
Fixed in
  • 1.35.9
envoyproxyenvoyAffected
  • <1.34.13
Fixed in
  • 1.34.13
GitHubenvoyproxy/envoypkg:github/envoyproxy/envoyOther threatsAffected
  • <1.34.13
Fixed in
  • 1.34.13

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should upgrade Envoy to the fixed versions 1.37.1, 1.36.5, 1.35.8, or 1.34.13 as soon as possible to eliminate the vulnerability. In environments where immediate upgrade is not feasible, consider deploying network-level protections such as HTTP/2 frame inspection and rate limiting to detect and block suspicious or malformed DATA frames arriving immediately after stream resets. Implement robust monitoring and alerting on Envoy proxy logs and metrics to detect abnormal crashes or restarts that may indicate exploitation attempts. Use canary or staged deployments to validate the stability of the patched versions before full rollout. Additionally, review and harden HTTP/2 traffic handling policies and consider isolating critical Envoy instances behind additional layers of defense to reduce exposure. Regularly audit and update all proxy and service mesh components to maintain security posture.

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, a logic vulnerability in Envoy's HTTP connection manager (FilterManager) that allows for Zombie Stream Filter Execution. This issue creates a "Use-After-Free" (UAF) or state-corruption window where filter callbacks are invoked on an HTTP stream that has already been logically reset and cleaned up. The vulnerability resides in source/common/http/filter_manager.cc within the FilterManager::decodeData method. The ActiveStream object remains valid in memory during the deferred deletion window. If a DATA frame arrives on this stream immediately after the reset (e.g., in the same packet processing cycle), the HTTP/2 codec invokes ActiveStream::decodeData, which cascades to FilterManager::decodeData. FilterManager::decodeData fails to check the saw_downstream_reset_ flag. It iterates over the decoder_filters_ list and invokes decodeData() on filters that have already received onDestroy(). This vulnerability is fixed in 1.37.1, 1.36.5, 1.35.8, and 1.34.13.

References

Community reviews

Loading reviews…