CVE-2026-53714
What it is
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, the xDS gRPC server in GatewayNamespaceMode, configured through provider.kubernetes.deploy.type=GatewayNamespace, installs a JWT StreamInterceptor but no UnaryInterceptor, leaving every unary Fetch RPC unauthenticated. The streaming interceptor also authenticates only discoveryv3.DeltaDiscoveryRequest messages; a discoveryv3.DiscoveryRequest used by the State-of-the-World protocol fails the type assertion and returns success without JWT validation. Any pod that can reach port 18000 can use the unauthenticated unary or State-of-the-World paths to retrieve TLS private keys through StreamSecrets, all xDS resources through StreamAggregatedResources, backend endpoints through StreamClusters or StreamEndpoints, and routing configuration through StreamRoutes or StreamListeners. This issue is fixed in versions 1.7.4 and 1.8.1.
At a glance
- Exploitability
- Can be exploited from the same network segment without logging in. High risk of data exposure.
- Exploit odds
- 0.3% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.3% in the next 30 days (EPSS).
- Severity: 7.4 HIGH (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.3% · EPSS, next 30 days
- Weakness
- CWE-306 · Missing authentication
- Record status
- Awaiting Analysis
Attack profile CVSS 3.1 · 7.4
- Attack vector
- Adjacent network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2026-53714.md and follow it. Check whether this project is affected by CVE-2026-53714. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://github.com/envoyproxy/gateway/commit/4df0809ff1ed59ffb09604da4084335b8c6647c5
- https://github.com/envoyproxy/gateway/commit/e9124abc4ff4b63a218a6890c1b28a982c850465
- https://github.com/envoyproxy/gateway/commit/f1f9829af2a231f0cae915c09800353c76622d97
- https://github.com/envoyproxy/gateway/pull/8986
- https://github.com/envoyproxy/gateway/pull/9116
- https://github.com/envoyproxy/gateway/pull/9118
- https://github.com/envoyproxy/gateway/releases/tag/v1.7.4
- https://github.com/envoyproxy/gateway/releases/tag/v1.8.1
- https://github.com/envoyproxy/gateway/security/advisories/GHSA-22xc-xg2r-9j7v
References
- https://github.com/envoyproxy/gateway/commit/4df0809ff1ed59ffb09604da4084335b8c6647c5
- https://github.com/envoyproxy/gateway/commit/e9124abc4ff4b63a218a6890c1b28a982c850465
- https://github.com/envoyproxy/gateway/commit/f1f9829af2a231f0cae915c09800353c76622d97
- https://github.com/envoyproxy/gateway/pull/8986
- https://github.com/envoyproxy/gateway/pull/9116
- https://github.com/envoyproxy/gateway/pull/9118
- https://github.com/envoyproxy/gateway/releases/tag/v1.7.4
- https://github.com/envoyproxy/gateway/releases/tag/v1.8.1
- https://github.com/envoyproxy/gateway/security/advisories/GHSA-22xc-xg2r-9j7v