CVE-2026-48706

Envoy Heap Buffer Overflow in TcpStatsdSink

HIGH
7.5
CVSS Score
Published: June 26, 2026 at 05:38 PM UTC
Updated: October 25, 2026 at 05:10 PM UTC
1 product affected across 1 vendorEnvoy

Using envoy by envoyproxy?

Get instant alerts when new vulnerabilities affect envoy - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.6%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.34.0 ≤ v < 1.35.131.36.0 ≤ v < 1.36.91.37.0 ≤ v < 1.37.51.38.0 ≤ v < 1.38.3
Affected range stops below 1.35.13, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.36.9, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.37.5, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.38.3, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

x_refsource_CONFIRMVendor AdvisoryMitigation
Source: cverecord
https://github.com/envoyproxy/envoy/security/advisories/GHSA-7q3f-gwg7-j8g4

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-120

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card