cve.bz

CVE-2026-53714 envoyproxy gateway

7.4 highEPSS 0.3%Fix available

High (7.4) in envoyproxy gateway. EPSS 0.3% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/envoyproxy/gateway 1.7.4, 1.8.1.

On this page
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.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
EPSS
0.3% (unchanged from 0.3% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 29th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-09-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-306 Missing Authentication for Critical Functionality
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-53714 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-53714?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-53714?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-53714 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

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

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-22xc-xg2r-9j7vGogithub.com/envoyproxy/gateway>=1.8.0-rc.0 <1.8.11.8.1
GHSA-22xc-xg2r-9j7vGogithub.com/envoyproxy/gateway<1.7.41.7.4
GO-2026-6003Gogithub.com/envoyproxy/gateway<1.7.4
>=1.8.0-rc.0 <1.8.1
1.7.4, 1.8.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
openSUSELeap 16.0govulncheck-vulndb0.0.20260723T184607-160000.1.1openSUSE-SU-2026:21483-1

From the distributions' data via OSV.dev: SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: openSUSE.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an unauthenticated pod within the cluster can bypass control plane authentication and extract critical cluster secrets, including private TLS keys and internal routing topologies. Although the potential blast radius involves sensitive credential disclosure across namespaces, the flaw is constrained to adjacent network access inside the Kubernetes cluster and specifically requires deployments configured in GatewayNamespaceMode. Environments operating under standard cluster-wide modes or enforcing strict network segmentation are significantly less exposed.

ProductPackageStateAdvisory
Red Hat Connectivity Link 1rhcl-1/rhcl-operator-bundleNot affected
Red Hat Connectivity Link 1rhcl-1/rhcl-rhel9-operatorNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-53714.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON