Envoy Proxy denial-of-service in HTTP filter with prefix_rewrite

Severity: info · Published 2026-10-12

Envoy Proxy, a widely-used network proxy component in Google Cloud Service Mesh, contains a denial-of-service vulnerability when HTTP filters modify request headers after route selection. An attacker can crash or disable the proxy by crafting specific requests, potentially disrupting service availability for applications relying on Cloud Service Mesh.

Technologies: Envoy Proxy, Google Cloud Platform. Vendors: Envoy Proxy, Google.

Quick answers

Is This vulnerability exploited in the wild?
No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?
Informational severity, published 12 October 2026.
Which products and versions are affected?
Envoy Proxy Envoy Proxy.
Is there a fix for This vulnerability?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is This vulnerability attacked?
It is attacked over the network, in a hosted service.
Am I affected?
Check whether you run Envoy Proxy or Google Cloud Platform. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A DoS vulnerability exists in Envoy Proxy when an HTTP filter such as ext_proc with route_cache_action: RETAIN mutates the :path header after route selection on a route configured with prefix_rewrite. The vulnerability requires network access and specific filter configuration. Exploitation causes denial of service.

Affected products

  • Envoy Proxy Envoy Proxy

Timeline

  • 2026-10-12: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.