CVE-2025-64763: Github.com/envoyproxy/envoy Envoy Forwards Early CONNECT Data Vulnerability

LOW
Advisory Identifier: GHSA-rj35-4m94-77jh
CVSS 3.7
CWE-693
Published
Advisory Summary

CVE-2025-64763 is a LOW (CVSS 3.7) envoy forwards early connect data vulnerability (CWE-693: Protection Mechanism Failure) affecting Github.com/envoyproxy/envoy libraries in the Go ecosystem. The issue involves envoy forwards early connect data in tcp proxy mode. Remediation is available by upgrading affected packages to version 1.36.3, 1.35.7, 1.34.11, 1.33.13.

CVE-2025-64763 at a Glance

CVE Identifier CVE-2025-64763
GHSA Identifier GHSA-rj35-4m94-77jh
Severity LOW
CVSS v3.1 Base Score 3.7
CWE Classification CWE-693: Protection Mechanism Failure
Affected Product Github.com/envoyproxy/envoy
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 3.7

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2025-64763

To remediate this vulnerability, upgrade all affected Github.com/envoyproxy/envoy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/envoyproxy/envoy fixed: 1.36.3
Upgrade github.com/envoyproxy/envoy to 1.36.3
github.com/envoyproxy/envoy fixed: 1.35.7
Upgrade github.com/envoyproxy/envoy to 1.35.7
github.com/envoyproxy/envoy fixed: 1.34.11
Upgrade github.com/envoyproxy/envoy to 1.34.11
github.com/envoyproxy/envoy fixed: 1.33.13
Upgrade github.com/envoyproxy/envoy to 1.33.13
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/envoyproxy/envoy

How to Check if You Are Affected

To determine whether your application is affected by CVE-2025-64763, inspect your project dependencies for Github.com/envoyproxy/envoy:

inspect dependencies for github.com/envoyproxy/envoy

Analyze the terminal output to locate any version of Github.com/envoyproxy/envoy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.36.3), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-693: Protection Mechanism Failure, where the product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. In Github.com/envoyproxy/envoy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

## 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)

CVE-2025-64763 Affected Github.com/envoyproxy/envoy Versions

4 component(s)
Fixed Versions:
1.36.31.35.71.34.111.33.13
Product / Package Ecosystem Affected Versions Fixed Version
github.com/envoyproxy/envoy
Go
≥ 1.36.0
< 1.36.3
1.36.3
github.com/envoyproxy/envoy
Go
≥ 1.35.0
< 1.35.7
1.35.7
github.com/envoyproxy/envoy
Go
≥ 1.34.0
< 1.34.11
1.34.11
github.com/envoyproxy/envoy
Go
< 1.33.13
1.33.13

References

Frequently Asked Questions

What is CVE-2025-64763?
CVE-2025-64763 is a security vulnerability in Github.com/envoyproxy/envoy involving Envoy forwards early CONNECT data in TCP proxy mode under CWE-693: Protection Mechanism Failure.
Which Github.com/envoyproxy/envoy versions are affected?
Affected versions include releases prior to 1.36.3, 1.35.7, 1.34.11, 1.33.13 across affected packages: github.com/envoyproxy/envoy.
What version fixes CVE-2025-64763?
Upgrading to 1.36.3, 1.35.7, 1.34.11, 1.33.13 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/envoyproxy/envoy affected?
Yes, github.com/envoyproxy/envoy is affected in releases prior to 1.36.3, 1.35.7, 1.34.11, 1.33.13. Upgrade your dependency to 1.36.3, 1.35.7, 1.34.11, 1.33.13 or later.
What is the CVSS score of CVE-2025-64763?
CVE-2025-64763 has a CVSS v3.1 base score of 3.7 (LOW) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N.
What CWE is associated with CVE-2025-64763?
CVE-2025-64763 is classified under CWE-693: Protection Mechanism Failure (The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.).
How can I check Go dependencies for CVE-2025-64763?
Run the dependency tree command: 'inspect dependencies for github.com/envoyproxy/envoy'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rj35-4m94-77jh",
  "modified" : "2025-12-10T20:03:48Z",
  "published" : "2025-12-05T18:12:51Z",
  "aliases" : [ "CVE-2025-64763" ],
  "summary" : "Envoy forwards early CONNECT data in TCP proxy mode",
  "details" : "## Summary\n\nForwarding of early CONNECT data in TCP proxy mode.\n\n## Details\n\nPer [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.\n\nThe 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. \n\n## Impact\n\nDe-synchronization of CONNECT tunnel state if a forwarding proxy upstream from Envoy responds with a non 2xx status.\n\n## Attack vector(s)\nSending data for a CONNECT request before receiving 2xx response.\n\n## Patches\nUsers should upgrade to v1.36.3, v1.35.7, v1.34.11 or v1.33.13\n\n## Credits\n\n[chasingimpact](https://github.com/chasingimpact) (Patrick)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/envoyproxy/envoy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.36.0"
      }, {
        "fixed" : "1.36.3"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.36.2"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/envoyproxy/envoy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.35.0"
      }, {
        "fixed" : "1.35.7"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.35.6"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/envoyproxy/envoy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.34.0"
      }, {
        "fixed" : "1.34.11"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.34.10"
    }
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/envoyproxy/envoy"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.33.13"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.33.12"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/envoyproxy/envoy/security/advisories/GHSA-rj35-4m94-77jh"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2025-64763"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/envoyproxy/envoy"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-693" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2025-12-05T18:12:51Z",
    "nvd_published_at" : "2025-12-03T18:15:47Z"
  }
}