CVSS 3.1
7.4 highCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:NHigh (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.
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:Ngithub.com/envoyproxy/gateway (Go): fixed in 1.8.1, 1.7.4Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| envoyproxy gateway | < 1.7.4 |
| envoyproxy gateway | >= 1.8.0-rc.0, < 1.8.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-22xc-xg2r-9j7v | Go | github.com/envoyproxy/gateway | >=1.8.0-rc.0 <1.8.1 | 1.8.1 |
| GHSA-22xc-xg2r-9j7v | Go | github.com/envoyproxy/gateway | <1.7.4 | 1.7.4 |
| GO-2026-6003 | Go | github.com/envoyproxy/gateway | <1.7.4 >=1.8.0-rc.0 <1.8.1 | 1.7.4, 1.8.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| openSUSE | Leap 16.0 | govulncheck-vulndb | 0.0.20260723T184607-160000.1.1 | openSUSE-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 rates this Important.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Connectivity Link 1 | rhcl-1/rhcl-operator-bundle | Not affected | |
| Red Hat Connectivity Link 1 | rhcl-1/rhcl-rhel9-operator | Not 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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.