# CVE-2026-47692: Other in envoy

> Attacker can smuggle bytes into upstream requests via malformed PROXY Protocol v2 headers, potentially corrupting data streams.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jun 2026
- **Updated:** 26 Jun 2026
- **Also known as:** BIT-envoy-2026-47692, GHSA-wh36-hm39-mm3r

## What is CVE-2026-47692?

CVE-2026-47692 is a medium-severity vulnerability in Envoyproxy Envoy, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-130 (Improper Handling of Length Parameter Inconsistency)

## Which versions are affected by CVE-2026-47692?

1 open source package ship an affected version, including envoy. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `envoy` | Bitnami | From 1.34.0 | 1.35.13, 1.36.9, 1.37.5, 1.38.3 |

Products: Envoyproxy Envoy.

## How do I fix CVE-2026-47692?

Upgrade envoy to a fixed version for your release line: 1.35.13, 1.36.9, 1.37.5 or 1.38.3.

## Is CVE-2026-47692 being exploited?

There is no known exploitation of CVE-2026-47692 in the wild and no public exploit code.

## Other vulnerabilities in Envoyproxy Envoy

- [CVE-2022-29226](https://insights.sbomify.com/CVE-2022-29226/): Trivial authentication bypass in Envoy (critical 10.0)
- [CVE-2019-18801](https://insights.sbomify.com/CVE-2019-18801/): Memory corruption in n/a (critical 9.8)
- [CVE-2019-18802](https://insights.sbomify.com/CVE-2019-18802/): Security feature bypass in n/a (critical 9.8)
- [CVE-2020-35470](https://insights.sbomify.com/CVE-2020-35470/): Information disclosure in n/a (high 8.8)
- [CVE-2024-23324](https://insights.sbomify.com/CVE-2024-23324/): Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-47692 and fix it if it is affected.

What it is: CVE-2026-47692 is a medium-severity vulnerability in Envoyproxy Envoy, published on 26 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-47692 in the wild and no public exploit code.

Affected packages and fixed versions:
- envoy (Bitnami): affected from 1.34.0; fixed in 1.35.13, 1.36.9, 1.37.5, 1.38.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-47692/ (Markdown: https://insights.sbomify.com/CVE-2026-47692/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-47692
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-47692
- OSV: https://osv.dev/vulnerability/CVE-2026-47692

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-47692/
Summaries are generated and may contain mistakes; the official description above is the record.