CVE-2025-54588: 
Envoy vulnerability analysis and mitigation

CVE-2025-54588 is a use-after-free (UAF) vulnerability in Envoy's DNS cache within the Dynamic Forward Proxy (DFP) implementation, classified as GHSA-g9vw-6pvx-7gmw. It affects Envoy versions 1.34.0 through 1.34.4 and 1.35.0, and was published on September 2, 2025, with NVD publication on September 3, 2025. The vulnerability causes abnormal process termination, resulting in a denial-of-service condition. It carries a CVSS v3.1 base score of 7.5 (High) (GitHub Advisory, Envoy Advisory).

The root cause is a use-after-free (CWE-416) in Envoy's Dynamic Forward Proxy implementation, introduced in v1.34.0. When a DNS resolution completion callback triggers new DNS resolutions or removes existing pending resolutions, Envoy may reallocate memory while a list iterator still holds a reference to the freed memory, leading to a segmentation fault and abnormal process termination. Exploitation requires three concurrent conditions: the Dynamic Forwarding Filter must be enabled, the envoy.reloadable_features.dfp_cluster_resolves_hosts runtime flag must be set to true, and the Host header must be modified between the Dynamic Forwarding Filter and Router filters. Detection of exploitation can be confirmed by the presence of the Envoy::Event::DispatcherImpl::runPostCallbacks() frame in the crash call stack (Envoy Advisory, GitHub Advisory).

Successful exploitation results in abnormal process termination of the Envoy proxy, causing a denial-of-service condition with high availability impact. There is no confidentiality or integrity impact — attackers cannot access or modify data through this vulnerability. In large-scale service-oriented architectures where Envoy serves as a critical L7 proxy or sidecar (e.g., Istio service meshes, Kubernetes ingress), a crash can disrupt traffic routing for all dependent services, potentially causing widespread service outages (Envoy Advisory, GitHub Advisory).

There is no public proof-of-concept exploit and no evidence of in-the-wild exploitation at this time (GitHub Advisory). The EPSS score is approximately 0.014% (3rd percentile), indicating a low near-term exploitation probability. The vulnerability is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog. Exploitation requires a specific non-default configuration (the dfp_cluster_resolves_hosts flag enabled alongside Host header modification), which limits the attack surface to intentionally configured deployments.

1. Reconnaissance: Identify Envoy proxy instances running versions 1.34.0–1.34.4 or 1.35.0, particularly those deployed as Dynamic Forward Proxies (e.g., in Istio or Kubernetes environments).
2. Verify configuration: Confirm that the target Envoy instance has the Dynamic Forwarding Filter enabled, the envoy.reloadable_features.dfp_cluster_resolves_hosts runtime flag set to true, and a filter chain that modifies the Host header between the DFP and Router filters.
3. Craft malicious request: Send HTTP requests with a Host header value that triggers DNS resolution via the DFP cluster. The Host header should be set to a value that causes the DFP filter to initiate DNS lookups.
4. Trigger race condition: Send concurrent or rapid successive requests designed to cause a DNS resolution completion callback to fire while new DNS resolutions are being initiated or existing pending resolutions are being removed, triggering the UAF condition.
5. Achieve DoS: The memory corruption causes Envoy to crash with a segmentation fault, observable via the Envoy::Event::DispatcherImpl::runPostCallbacks() frame in the call stack, resulting in process termination and service disruption (Envoy Advisory).

• Process: Abnormal Envoy process termination (segmentation fault / SIGSEGV); crash dumps containing the Envoy::Event::DispatcherImpl::runPostCallbacks() frame in the call stack.
• Logs: Envoy error logs showing unexpected process exits or crash reports; repeated Envoy restarts logged by the container orchestrator (e.g., Kubernetes pod restart events with CrashLoopBackOff).
• Network: Unusual volume of HTTP requests with varying or crafted Host headers targeting a DFP-configured Envoy instance; DNS resolution spikes correlating with process crashes.
• System: Core dump files generated by the Envoy process in the working directory or configured core dump path (Envoy Advisory).

Users should upgrade Envoy to version 1.34.5 or 1.35.1, which contain the fix for this vulnerability (Envoy v1.34.5 Release, Envoy v1.35.1 Release). As an immediate workaround without upgrading, set the envoy.reloadable_features.dfp_cluster_resolves_hosts runtime flag to false, which disables the vulnerable code path. Additionally, review filter chain configurations to determine whether Host header modification between the Dynamic Forwarding Filter and Router filters is necessary, and restrict it if not required (Envoy Advisory). Istio users should consult the Istio security advisory (ISTIO-SECURITY-2025-001) for guidance specific to their deployments.

The Istio project published a security advisory (ISTIO-SECURITY-2025-001) addressing this vulnerability, reflecting its relevance to service mesh deployments that rely on Envoy as a data plane component. The vulnerability was credited to Rohit Agrawal from Databricks, indicating it was discovered through internal security research at a major cloud data platform company. Security news outlets such as SecurityOnline.info covered the vulnerability alongside a companion session hijacking flaw (CVE-2025-55162), noting the dual DoS and session hijacking risks patched in the same Envoy release cycle. The CISA weekly vulnerability bulletin for the week of September 1, 2025 also referenced this CVE.