envoyproxy · Envoy · published 2026-06-26

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

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-47692 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 12% of all CVEs. This Envoy vulnerability: CVSS 4.8 (v3.1). Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in Envoy 1.38.3, 1.37.5, 1.36.9, 1.35.13.

Patch events

  1. This monthSecurity release

    Web serverEnvoy

    Envoy security releases: 1.38.3, 1.37.5, 1.36.9, 1.35.13

    Upgrade to 1.38.31.37.51.36.91.35.13

    Why: CVE-2026-47220: Public proof-of-concept exists (SSVC exploitation: poc).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (13th pct)FIRST EPSS v2026.06.15
CVSS base score4.8 (v3.1)
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →