Vulnerability in Envoyproxy (CVE-2026-48044)
Summary
Vulnerability in Envoyproxy (CVE-2026-48044). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.35.11 or later.
Original description
The description as published by the source.
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.23.0 until 1.35.11, 1.36.7, 1.37.3, and 1.38.1, a vulnerability has been identified in Envoy's zstd decompressor implementation (ZstdDecompressorImpl). When zstd decompression is enabled, processing a specially crafted, highly compressed zstd payload can lead to massive memory allocation. An attacker can exploit this to cause severe memory exhaustion, potentially resulting in an Out-Of-Memory (OOM) kill and Denial of Service (DoS) for the Envoy proxy. This vulnerability is fixed in 1.35.11, 1.36.7, 1.37.3, and 1.38.1.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-48044 has been found in Envoyproxy.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade Envoyproxy to 1.35.11 or later.
If unsure, ask your IT team or search "Envoyproxy CVE-2026-48044" on the vendor's site.
CVE-2026-48044 (Envoyproxy) — CWE-409 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.35.11 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-409) exists in Envoyproxy.
Check the vendor advisory for the affected versions of Envoyproxy.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.35.11.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'Envoyproxy' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Envoyproxy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
Envoyproxyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade Envoyproxy to 1.35.11ステージング環境で 1.35.11 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- exploit security-advisories@github.com