https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-08T12:57:36.387402+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/bit-envoy-2025-64763 BIT-envoy-2025-64763 — Envoy forwards early CONNECT data in TCP proxy mode 2026-10-08T12:57:36.439441+00:00

Affected: Bitnami: envoy

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.reloadable_features.reject_early_connect_data 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.

 https://cve.radiocsirt.org/vuln/euvd-2026-262469 EUVD-2026-262469 2026-10-08T12:57:36.439553+00:00 EUVD-2026-262469 https://cve.radiocsirt.org/vuln/fkie_cve-2025-64763 fkie_cve-2025-64763 2026-10-08T12:57:36.439570+00:00

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.reloadable_features.reject_early_connect_data 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.

 https://cve.radiocsirt.org/vuln/ghsa-rj35-4m94-77jh GHSA-rj35-4m94-77jh — Envoy forwards early CONNECT data in TCP proxy mode 2026-10-08T12:57:36.439599+00:00

Affected: Go: github.com/envoyproxy/envoy

## Summary

Forwarding of early CONNECT data in TCP proxy mode.

## Details

Per [RFC 7231-4.3.6](https://www.rfc-editor.org/rfc/rfc7231#section-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](https://github.com/chasingimpact) (Patrick)