CVE-2025-64763: Envoy forwards early CONNECT data in TCP proxy mode
Summary Forwarding of early CONNECT data in TCP proxy mode. Details Per RFC 7231-4.3.6 the sender of CONNECT (and all inbound proxies) switch to tunnel mode only after receiving 2xx response. However in TCP proxy mode, Envoy accepts client data before it has issued a 2xx response and eagerly proxies it to an established TCP connection.
Published Dec 5, 2025 · Updated Dec 10, 2025
Affected packages
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.36.0, <= 1.36.2
- Fixed in
- 1.36.3
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.35.0, <= 1.35.6
- Fixed in
- 1.35.7
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- >= 1.34.0, <= 1.34.10
- Fixed in
- 1.34.11
- Check
go list -m github.com/envoyproxy/envoy
github.com/envoyproxy/envoy
- Ecosystem
- Go
- Affected
- <= 1.33.12
- Fixed in
- 1.33.13
- Check
go list -m github.com/envoyproxy/envoy
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Forwarding of early CONNECT data in TCP proxy mode.
Details
Per RFC 7231-4.3.6 the sender of CONNECT (and all inbound proxies) switch to tunnel mode only after receiving 2xx response. However in TCP proxy mode, Envoy accepts client data before it has issued a 2xx response and eagerly proxies it to an established TCP connection. This creates possibility of a de-synchronized tunnel state if a proxy upstream from Envoy responds with a status other an 2xx.
The RFC does not specify the behavior in case an early CONNECT data is received and early CONNECT data is common as a latency reduction mechanism. To prevent disruption to existing deployments Envoy will by default allow early CONNECT data. Setting the envoy.reloadable_features.reject_early_connect_data runtime flag to true will cause CONNECT requests that send data before 2xx response to be rejected. This options should be enabled if there are intermediaries upstream from Envoy that may reject establishment of a CONNECT tunnel.
Impact
De-synchronization of CONNECT tunnel state if a forwarding proxy upstream from Envoy responds with a non 2xx status.
Attack vector(s)
Sending data for a CONNECT request before receiving 2xx response.
Patches
Users should upgrade to v1.36.3, v1.35.7, v1.34.11 or v1.33.13
Credits
chasingimpact (Patrick)
Credited to botengyao, phlax, yanavlasov, agrawroh, chasingimpact.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-26308
Envoy has RBAC Header Validation Bypass via Multi-Value Header Concatenation
high7.5Mar 10, 2026CVE-2026-26309
Envoy affected by off-by-one write in JsonEscaper::escapeString()
medium5.3No fixMar 10, 2026CVE-2026-26310
Envoy vulnerable to crash for scoped ip address during DNS
medium5.9No fixMar 10, 2026CVE-2026-26311
Envoy: HTTP - filter chain execution on reset streams causing UAF crash
medium5.9No fixMar 10, 2026CVE-2026-26330
Envoy's global rate limit may crash when the response phase limit is enabled and the response phase request is failed directly
medium5.3No fixMar 10, 2026CVE-2025-64527
Envoy crashes when JWT authentication is configured with the remote JWKS fetching
medium6.5Dec 5, 2025
