Skip to content
VulniPulse
Sign in
Advisory severityMedium4.8Red Hat Linux

Medium [CVE-2026-47692] PROXY Protocol v2 header generator emits "skipped" TLVs, causing 65 KB attacker-controlled spillover into the upstream application stream

This medium-severity Red Hat Linux advisory covers CVE-2026-47692 affecting OpenShift Service Mesh 2, OpenShift Service Mesh 3.

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

CVE-2026-47692 Source published Source updated

VulniPulse record published Record updated

CVE-2026-47692
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, PROXY Protocol v2 header generator emits TLVs beyond the maximum length of 65535 bytes, causing a mismatch between bytes written and the length field in the header.

This can result in smuggled bytes on the upstream request. This vulnerability is fixed in 1.35.13, 1.36.9, 1.37.5, and 1.38.3.

A flaw was found in Envoy. An attacker on an adjacent network could exploit this to smuggle bytes into upstream requests.

This could potentially bypass security mechanisms or lead to unexpected behavior in how requests are processed. This flaw allows for up to 65 KB of attacker-controlled data to be smuggled into the upstream request, potentially bypassing security controls or corrupting data.

This primarily affects deployments where Envoy is configured to use PROXY Protocol v2. Red Hat severity: Moderate — CVSS 4.8 (CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L).

Weakness: CWE-130. Affected Red Hat products: OpenShift Service Mesh 2; OpenShift Service Mesh 3.

Red Hat does not currently list a fixing RHSA for this CVE.

Is CVE-2026-47692 exploited?

No exploitation is reported in the sources VulniPulse tracks: CVE-2026-47692 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-47692?

Upgrade to a fixed release named by Red Hat:

  • 1.35.13
  • 1.36.9
  • 1.37.5
  • 1.38.3

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

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

More Red Hat Linux advisories

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.

Download on the App StoreGet CVE alerts on AndroidSee app features

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.