● Medium · CVSS 5.9

How to Fix CVE-2026-26311: Envoy HTTP: filter chain execution on reset streams causing UAF crash

Q: Is CVE-2026-26311 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-26311?

CVSS rates it 5.9 (Medium). Use that score to set your patch priority next to the other items in your queue.

Q: Do I have to take envoy offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-26311 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-30982: iccDEV has a heap out-of-bounds read in CIccPcsXform::pushXYZConvert() — iccDEV has a heap out-of-bounds read in CIccPcsXform::pushXYZConvert()
How to Fix CVE-2026-20982: Path Traversal in Samsung Mobile Devices — Path Traversal in Samsung Mobile Devices
How to Fix CVE-2026-41935: Critical Vulnerability in Vvveb , Critical Vulnerability in Vvveb
How to Fix CVE-2026-22206: Sql injection in SPIP , Sql injection in SPIP
How to Fix CVE-2026-0956: Out-Of-Bounds Read in Digilent DASYLab in DASYLab , Out-Of-Bounds Read in Digilent DASYLab in DASYLab

*By Sai Kiran Pandrala*

⚡ At a glance


Severity	CVSS 5.9, Medium
Actively exploited?	No
Affected	Envoyproxy envoy (>= 1.37.0, < 1.37.1, >= 1.36.0, < 1.36.5, >= 1.35.0, < 1.35.9)
Fixed in	1.37.1, 1.36.5, 1.35.9, 1.34.13
Type (CWE)	CWE-416: Use After Free

What is CVE-2026-26311?

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.

In practical terms, a successful attacker gets use-after-free that can lead to heap corruption and code execution. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You're affected if you run Envoyproxy envoy at any version in the Affected row above. Use these probes to find your installed build:


# Confirm the installed version via your package manager
dpkg -l | grep -i envoy   # Debian/Ubuntu
rpm -qa | grep -i envoy   # RHEL/CentOS/Rocky

How to fix CVE-2026-26311

The primary fix is to upgrade to the patched build listed in the Fixed in row above (1.37.1, 1.36.5, 1.35.9, 1.34.13). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


sudo apt-get update
sudo apt-get install --only-upgrade envoy
# Confirm the installed version meets or exceeds 1.37.1
dpkg -s envoy | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security envoy -y
rpm -q envoy

Windows (PowerShell, admin)


# Try winget first
winget upgrade --id 'Envoyproxy.envoy' --silent --accept-source-agreements --accept-package-agreements
# If winget does not know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\envoy-1.37.1.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows) - detect, back up, upgrade, verify, log


# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\envoy-Patch-CVE-2026-26311.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-26311 remediation for Envoyproxy envoy"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*envoy*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'1.37.1') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\envoy-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
# Adjust the source path to match your install
$src = "$env:ProgramFiles\Envoyproxy\envoy"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer (place the verified file on a share or staging path)
$installer = "$env:TEMP\envoy-1.37.1.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*envoy*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'1.37.1') {
    Write-Log "SUCCESS: now at $verify (>= 1.37.1)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux) - detect, back up, upgrade, verify, log


#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/envoy-patch-cve-2026-26311.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-26311 remediation for Envoyproxy envoy"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s envoy >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' envoy)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q envoy >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' envoy)
    PKG_MGR=dnf
else
    log "envoy not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: envoy=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/envoy-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/envoy /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y envoy
else
    sudo dnf upgrade --security -y envoy
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' envoy)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' envoy)
fi
log "After upgrade: $NEW"

# Optionally compare against 1.37.1 with dpkg --compare-versions or sort -V
log "Done. Restart the affected service if the package install did not."

If you can't patch immediately

These are runnable hardening commands. They reduce blast radius but they're not a replacement for the vendor patch.

No official vendor workaround is published for this CVE; patching is the only documented fix. The runnable hardening below is generic defense in depth, not a substitute for the patch.

Restrict the affected service to trusted networks (Linux):


# Vendor advisory: https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px
# Replace <port> with the affected service port and 10.0.0.0/24 with your admin subnet
sudo iptables -A INPUT -p tcp --dport <port> -s 10.0.0.0/24 -j ACCEPT
sudo iptables -A INPUT -p tcp --dport <port> -j DROP

Windows Firewall equivalent:


# Vendor advisory: https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px
New-NetFirewallRule -DisplayName 'Allow affected service from admin subnet' \
    -Direction Inbound -Action Allow -Protocol TCP -LocalPort <port> -RemoteAddress 10.0.0.0/24
New-NetFirewallRule -DisplayName 'Block affected service from everywhere else' \
    -Direction Inbound -Action Block -Protocol TCP -LocalPort <port>

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


# Confirm the running build matches the patched version listed by the vendor
# Example for Linux package installs:
dpkg -l | grep -i "envoy"   # Debian/Ubuntu
rpm -qa | grep -i "envoy"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed 1.37.1.

Then re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-26311 has cleared. Sweep your logs for the indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-26311 being actively exploited?