Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
5.9

CVE-2026-48706: Envoy proxy crash or code exec from long metric names

CVE-2026-48706 · published 4 months ago
Summary

Versions of Envoy proxy between 1.34.0 and 1.38.3 can mishandle very long statistic names, causing it to write past its own memory. This can make the service stop working or, in rare cases, allow an attacker to run code on the server. Update to Envoy 1.35.13, 1.36.9, 1.37.5, or 1.38.3 to fix the problem.

What to do

The CVE record does not list a fixed version. Check the vendor's site or the advisory links below - a fix may already be released.

Affected software
VendorProductAffected versions
envoyproxy envoy >= 1.34.0, < 1.35.13
>= 1.36.0, < 1.36.9
>= 1.37.0, < 1.37.5
>= 1.38.0, < 1.38.3
cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
Original advisory text
Envoy Heap Buffer Overflow in TcpStatsdSink
Envoy is an open source edge and service proxy designed for cloud-native applications. From 1.34.0 until 1.35.13, 1.36.9, 1.37.5, and 1.38.3, a vulnerability exists in Envoy's TCP StatsD sink (TcpStatsdSink), where the thread-local flusher buffer can be overflowed by exceptionally long statistic names (e.g., >16KiB). During formatting, TcpStatsdSink reserves a single contiguous memory slice of 16KiB (FLUSH_SLICE_SIZE_BYTES). If formatting a single metric exceeds the remaining capacity, the flusher initiates a buffer rotation but incorrectly continues to allocate another fixed 16KiB slice. If an attacker can trigger a statistic name longer than 16KiB—for example, by sending an HTTP or gRPC request with an extremely long request path (:path) that is recorded by the grpc_stats filter configured with stats_for_all_methods: true—the flusher will attempt to copy the metric name using memcpy operations beyond the allocated heap buffer boundaries. This leads to a heap write overflow, which can cause immediate denial-of-service (process crash) or potential remote code execution (RCE). This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
Fix within
Internet-facing 60 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker partial control
Severity
5.9 Medium
Exploitation
<1% chance of attack within 30 days
Type
CWE-120Classic Buffer Overflow
Timeline
Published26 Jun 2026
Updated4 Nov 2026
First seen26 Jun 2026
Sources
Track software like this
Free during beta