Skip to content
VulniPulse
Advisory severityMedium5.9Red Hat Linux

Medium [CVE-2026-48706] Envoy Heap Buffer Overflow in TcpStatsdSink

This medium-severity Red Hat Linux advisory covers CVE-2026-48706 affecting Red Hat OpenShift Service Mesh 3.1, Red Hat OpenShift Service Mesh 3.2, Red Hat OpenShift Service Mesh 3.3.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-48706 Source published Source updated

VulniPulse record published Record updated

CVE-2026-48706
Affected products & platforms
Red Hat LinuxUnclassified
Open source advisory

Summary

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.

An attacker can exploit a heap write overflow vulnerability in Envoy's TCP StatsD sink by sending exceptionally long statistic names, such as those found in HTTP or gRPC request paths.

Is CVE-2026-48706 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-48706 is not in the CISA KEV catalog (checked ) and this advisory does not report exploitation. That is not proof the vulnerability cannot be exploited.

How do I fix CVE-2026-48706?

Upgrade to a fixed release named by Red Hat:

  • 1.35.13
  • 1.36.9
  • 1.37.5
  • 1.38.3
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953556
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953743
  • openshift-service-mesh/istio-proxyv2-rhel9:1784908639
  • RHSA-2026:49729
  • RHSA-2026:49744
  • RHSA-2026:49765

Confirm against the vendor advisory before you patch.

Affected versions

No affected-version range was extracted from the source record. The vendor advisory is authoritative. Check it before change work.

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Fixed versions
  • 1.35.13
  • 1.36.9
  • 1.37.5
  • 1.38.3
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953556
  • openshift-service-mesh/istio-proxyv2-rhel9:1784953743
  • openshift-service-mesh/istio-proxyv2-rhel9:1784908639
  • RHSA-2026:49729
  • RHSA-2026:49744
  • RHSA-2026:49765

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

Official advisory · high-confidence parse· fetched 13 days ago·verify at source

Get an email when Red Hat publishes the next one.

See Red Hat's last 90 days of advisories first. Then choose one product with live alerts free for life, or a free month of real-time alerts on everything with the severity, the fixed version and the vendor's link (card needed, then US$15/month; we email you before the first charge).

Alert me about Red Hat
All Red Hat Linux advisories

iPhone and Android apps · New on the App Store

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.