CVE-2025-64763: Envoy is a high-performance edge/middle/service proxy.
Medium CVSS 5.3
- CVE id
- CVE-2025-64763
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.33.13 >= 1.34.0, < 1.34.11 >= 1.35.0, < 1.35.7 >= 1.36.0, < 1.36.3 |
1.33.13, 1.34.11, 1.35.7, 1.36.3 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.33.13, 1.34.11, 1.35.7, 1.36.3.
envoy --version
- Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
Envoy is a high-performance edge/middle/service proxy. In 1.33.12, 1.34.10, 1.35.6, 1.36.2, and earlier, when Envoy is configured in TCP proxy mode to handle CONNECT requests, it accepts client data before issuing a 2xx response and forwards that data to the upstream TCP connection. If a forwarding proxy upstream from Envoy then responds with a non-2xx status, this can cause a de-synchronized CONNECT tunnel state. By default Envoy continues to allow early CONNECT data to avoid disrupting existing deployments. The envoy.reloadablefeatures.rejectearlyconnectdata runtime flag can be set to reject CONNECT requests that send data before a 2xx response when intermediaries upstream from Envoy may reject establishment of a CONNECT tunnel.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.