Envoy Gateway: xDS Control Plane Information Disclosure when operating in GatewayNamespaceMode

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.4 · CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N

EPSS

• CVE-2026-53714: 0.35% estimated exploitation activity in the next 30 days; percentile 28.44 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact When Envoy Gateway runs in GatewayNamespaceMode (provider.kubernetes.deploy.type=GatewayNamespace), the xDS gRPC server is configured with a StreamInterceptor for JWT authentication but no UnaryInterceptor. The go-control-plane xDS server exposes both streaming and unary (Fetch) RPC methods for all registered discovery services. Since there is no unary interceptor, these Fetch endpoints are completely unauthenticated. Additionally, the JWT authentication interceptor in GatewayNamespaceMode only validates tokens when the received gRPC message is of type discoveryv3.DeltaDiscoveryRequest . If the message is a discoveryv3.DiscoveryRequest — used by the State-of-the-World (SotW) xDS protocol — the type assertion fails, the validation block is skipped entirely, and RecvMsg returns nil (success) without any authentication. Any pod in the cluster that can reach the xDS server (port 18000) can use the SotW protocol to bypass JWT authentication and access: TLS private keys via…

Published by the source

16 Jul 2026, 19:32 UTC

Last modified by the source

16 Jul 2026, 19:32 UTC

Source last checked

26 Oct 2026, 15:25 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-22xc-xg2r-9j7v

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-53714

Advisory: Envoy Gateway: xDS Control Plane Information Disclosure when operating in GatewayNamespaceMode
IDs: CVE-2026-53714, GHSA-22xc-xg2r-9j7v
Record: https://patchnext.com/advisories/cve-2026-53714 (revision 1, source checked 26 Oct 2026, 15:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/envoyproxy/gateway 1.8.1, 1.7.4. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/envoyproxy/gateway: affected >= 1.8.0-rc.0, < 1.8.1; < 1.7.4; fixed in 1.8.1, 1.7.4

## Suggested inspection (read-only)
- Go github.com/envoyproxy/gateway: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/envoyproxy/gateway.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-22xc-xg2r-9j7v (GitHub-reviewed advisory GHSA-22xc-xg2r-9j7v lists affected ranges: Go github.com/envoyproxy/gateway >=1.8.0-rc.0 =0 <1.7.4)

Commands are suggestions: review each one before running it.