Is CVE-2026-53714 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-53714 being exploited in the wild.

How severe is CVE-2026-53714?

High severity, with a CVSS score of 7.4, published 14 September 2026.

Which products and versions are affected?

github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.

Is there a fix for CVE-2026-53714?

Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-53714 attacked?

It is attacked from the adjacent network, in a software library.

Am I affected by CVE-2026-53714?

Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-53714: Envoy Gateway authentication bypass in xDS control plane

CVE-2026-53714 · Severity: high · CVSS 7.4 · Published 2026-09-14

Envoy Gateway, a tool used to manage network traffic in Kubernetes environments, contains a security flaw when configured in a specific multi-tenant mode. An attacker with access to the internal network can bypass security checks to steal sensitive information, including TLS private keys and internal routing rules. This could allow an unauthorized party to intercept encrypted traffic or gain deep insight into the internal network structure.

Technologies: github.com/envoyproxy/gateway (Go). Vendors: Go.

Quick answers

Is CVE-2026-53714 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-53714 being exploited in the wild.
How severe is CVE-2026-53714?: High severity, with a CVSS score of 7.4, published 14 September 2026.
Which products and versions are affected?: github.com/envoyproxy/gateway (Go) SEMVER:introduced=0,fixed=1.7.4,introduced=1.8.0-rc.0,fixed=1.8.1, SEMVER:introduced=1.8.0-rc.0,fixed=1.8.1.
Is there a fix for CVE-2026-53714?: Yes. github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-53714 attacked?: It is attacked from the adjacent network, in a software library.
Am I affected by CVE-2026-53714?: Check whether you run github.com/envoyproxy/gateway (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/envoyproxy/gateway (Go): upgrade to 1.8.1 or later
```
go get github.com/envoyproxy/gateway@v1.8.1
```

Technical details

Envoy Gateway is vulnerable to an authentication bypass in its xDS gRPC server when running in GatewayNamespaceMode. The server lacks a UnaryInterceptor for JWT authentication, leaving Fetch RPC methods completely unauthenticated. Furthermore, the existing StreamInterceptor fails to validate tokens for State-of-the-World (SotW) DiscoveryRequests due to an incorrect type assertion that only checks for DeltaDiscoveryRequests. An attacker within the cluster network can exploit these omissions to access sensitive xDS resources, including Secrets (SDS), Clusters (CDS), and Routes (RDS). The issue is fixed in versions 1.8.1 and 1.7.4.

Affected products

envoyproxy gateway >= 1.8.0-rc.0, < 1.8.1; < 1.7.4

Identifiers

CVE-2026-53714
GHSA-22xc-xg2r-9j7v
GO-2026-6003

Timeline

2026-06-05: disclosed
2026-07-16: advisory
2026-07-16: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.