Cyber Resilience

CVE-2026-47692

Envoyproxy Envoy 1.34.0 – 1.35.13

Published
26 June 2026
Modified
27 June 2026
Patch / advisory
CVSS Score v3.1 4.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L
EPSS Score 0.0022 12th percentile
Risk Priority 32 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-47692 is a medium-severity Improper Handling of Length Parameter Inconsistency (CWE-130) vulnerability in Envoyproxy Envoy. Its CVSS base score is 4.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 12th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-48090Same product: Envoyproxy Envoy
CVE-2023-27488Same product: Envoyproxy Envoy
CVE-2026-26309Same product: Envoyproxy Envoy
CVE-2026-26330Same product: Envoyproxy Envoy
CVE-2026-47205Same product: Envoyproxy Envoy
CVE-2025-54588Same product: Envoyproxy Envoy
CVE-2023-27496Same product: Envoyproxy Envoy
CVE-2024-39305Same product: Envoyproxy Envoy
CVE-2026-48706Same product: Envoyproxy Envoy
CVE-2024-32975Same product: Envoyproxy Envoy

Affected Assets

envoyproxy
envoy
1.34.0 — 1.35.13 · 1.36.0 — 1.36.9 · 1.37.0 — 1.37.5

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.5
  • V4.2.1
  • V4.2.2

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can discover length-parameter inconsistencies through targeted parsing tests.

Input validation enforces correct length-to-data consistency checks on parsed messages before processing.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly enforce length validation and input sanitization during coding and review.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development can detect length-inconsistency vulnerabilities before deployment.

prevents

Secure development lifecycle mandates input validation and length checks that directly address inconsistent length fields.

prevents

Application security requirements include explicit rules for handling message lengths and data structures.

prevents

Secure architecture principles require robust parsing and bounds checking to prevent length-related flaws.

prevents

Secure coding standards directly prohibit improper length handling and enforce defensive parsing practices.

References