CVE-2026-47692: CWE-130: Improper Handling of Length Parameter Inconsistency in envoyproxy envoy
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.
AI Analysis
Technical Summary
CVE-2026-47692 describes an improper handling of length parameter inconsistency (CWE-130) in the Envoy proxy's PROXY Protocol v2 header generator. Specifically, in versions from 1.34.0 until the fixed versions, the generator emits TLVs beyond the maximum length of 65535 bytes. This causes a mismatch between the actual bytes written and the length field in the header, potentially allowing smuggled bytes to be sent upstream. The vulnerability has a CVSS 3.1 base score of 4.8 (medium severity), with attack vector being adjacent network, low attack complexity, high privileges required, no user interaction, scope changed, no confidentiality impact, low integrity impact, and low availability impact. The issue is fixed in versions 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
Potential Impact
The vulnerability can cause smuggling of bytes on upstream requests due to length field inconsistencies in the PROXY Protocol v2 header. This may lead to integrity and availability impacts as indicated by the CVSS vector, but no confidentiality impact is noted. Exploitation requires high privileges and access from an adjacent network. No known exploits are reported in the wild.
Mitigation Recommendations
Fixed versions are 1.35.13, 1.36.9, 1.37.5, and 1.38.3. Users should upgrade to these versions to remediate the vulnerability. Patch status is confirmed by the description indicating these versions contain the fix. No additional vendor advisory was provided. No cloud service is involved, so remediation depends on user upgrades.
CVE-2026-47692: CWE-130: Improper Handling of Length Parameter Inconsistency in envoyproxy envoy
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, 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.
CVSS v3.1
Score 4.8medium
Affected software
pkg:github/envoyproxy/envoyRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-47692 describes an improper handling of length parameter inconsistency (CWE-130) in the Envoy proxy's PROXY Protocol v2 header generator. Specifically, in versions from 1.34.0 until the fixed versions, the generator emits TLVs beyond the maximum length of 65535 bytes. This causes a mismatch between the actual bytes written and the length field in the header, potentially allowing smuggled bytes to be sent upstream. The vulnerability has a CVSS 3.1 base score of 4.8 (medium severity), with attack vector being adjacent network, low attack complexity, high privileges required, no user interaction, scope changed, no confidentiality impact, low integrity impact, and low availability impact. The issue is fixed in versions 1.35.13, 1.36.9, 1.37.5, and 1.38.3.
Potential Impact
The vulnerability can cause smuggling of bytes on upstream requests due to length field inconsistencies in the PROXY Protocol v2 header. This may lead to integrity and availability impacts as indicated by the CVSS vector, but no confidentiality impact is noted. Exploitation requires high privileges and access from an adjacent network. No known exploits are reported in the wild.
Mitigation Recommendations
Fixed versions are 1.35.13, 1.36.9, 1.37.5, and 1.38.3. Users should upgrade to these versions to remediate the vulnerability. Patch status is confirmed by the description indicating these versions contain the fix. No additional vendor advisory was provided. No cloud service is involved, so remediation depends on user upgrades.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-19T21:18:20.403Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3ec10ed9e07477746fae18
Added to database: 06/26/2026, 18:12:30 UTC
Last enriched: 06/26/2026, 18:23:08 UTC
Last updated: 08/10/2026, 12:41:11 UTC
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.