{"answers":{"affected":"6 open source packages ship an affected version, including github.com/envoyproxy/gateway and envoy-gateway.","exploited":"There is no known exploitation of CVE-2026-53714 in the wild and no public exploit code.","fix":"Upgrade github.com/envoyproxy/gateway to a fixed version for your release line: 1.7.4 or 1.8.1.","what":"CVE-2026-53714 is a high-severity missing authorization vulnerability in envoyproxy gateway, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-53714 and fix it if it is affected.\n\nWhat it is: CVE-2026-53714 is a high-severity missing authorization vulnerability in envoyproxy gateway, published on 14 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-53714 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/envoyproxy/gateway (Go): affected all versions; fixed in 1.7.4, 1.8.1\n- github.com/envoyproxy/gateway (Go): affected all versions; fixed in 1.7.4\n- github.com/envoyproxy/gateway (Go): affected all versions; fixed in 1.7.4\n- github.com/envoyproxy/gateway (Go): affected from 1.8.0-rc.0; fixed in 1.8.1\n- github.com/envoyproxy/gateway (Go): affected from 1.8.0-rc.0; fixed in 1.8.1\n- envoy-gateway (Bitnami): affected all versions; fixed in 1.7.4, 1.8.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-53714/ (Markdown: https://insights.sbomify.com/CVE-2026-53714/index.md)","id":"CVE-2026-53714","markdown":"https://insights.sbomify.com/CVE-2026-53714/index.md","name":"CVE-2026-53714","record":{"aliases":["BIT-envoy-gateway-2026-53714","CLEANSTART-2026-BF33311","CLEANSTART-2026-VG58591","GHSA-22xc-xg2r-9j7v","GO-2026-6003","MINI-fmc4-9j2r-fh6c","MINI-mm7x-hfwm-3gqh","MINI-qm5h-5q72-vj3f","MINI-rh53-hr7q-75rj","ROOT-APP-GOBINARY-CVE-2026-53714"],"analysis":{"component_type":"cloud_service","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Envoy Gateway","requires_auth":"none","summary":"Attackers with network access can retrieve sensitive TLS keys and routing configs from Envoy Gateway when GatewayNamespaceMode is enabled due to missing authentication on specific RPCs.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"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.","ecosystems":["Bitnami","Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Envoy Gateway: xDS Control Plane Information Disclosure when Envoy Gateway operates in GatewayNamespaceMode","id":"CVE-2026-53714","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":6,"n_references":9,"next":{"headline":"Envoy Gateway: Wasm cache ServeHTTP reads mappingPath2Cache without lock","id":"CVE-2026-53715"},"packages":[{"ecosystem":"Bitnami","fixed":["1.7.4","1.8.1"],"introduced":["0","1.8.0"],"last_affected":[],"package":"envoy-gateway","purl":"pkg:bitnami/envoy-gateway","source":"BIT-envoy-gateway-2026-53714"},{"ecosystem":"Go","fixed":["1.7.4","1.8.1"],"introduced":["0","1.8.0-rc.0"],"last_affected":[],"package":"github.com/envoyproxy/gateway","purl":"pkg:golang/github.com/envoyproxy/gateway","source":"GO-2026-6003"},{"ecosystem":"Go","fixed":["1.7.4"],"introduced":["0"],"last_affected":[],"package":"github.com/envoyproxy/gateway","purl":null,"source":"GHSA-22xc-xg2r-9j7v"},{"ecosystem":"Go","fixed":["1.7.4"],"introduced":["0"],"last_affected":[],"package":"github.com/envoyproxy/gateway","purl":"pkg:golang/github.com/envoyproxy/gateway","source":"GHSA-22xc-xg2r-9j7v"},{"ecosystem":"Go","fixed":["1.8.1"],"introduced":["1.8.0-rc.0"],"last_affected":[],"package":"github.com/envoyproxy/gateway","purl":null,"source":"GHSA-22xc-xg2r-9j7v"},{"ecosystem":"Go","fixed":["1.8.1"],"introduced":["1.8.0-rc.0"],"last_affected":[],"package":"github.com/envoyproxy/gateway","purl":"pkg:golang/github.com/envoyproxy/gateway","source":"GHSA-22xc-xg2r-9j7v"}],"prev":{"headline":"Envoy Gateway: Authentication Bypass via Improper Input Validation in EnvoyExtensionPolicy Lua Allows Secret Disclosure","id":"CVE-2026-53713"},"products":["gateway"],"published":"2026-09-14","related":[],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-15","vendors":["envoyproxy"]},"summary":"Attackers with network access can retrieve sensitive TLS keys and routing configs from Envoy Gateway when GatewayNamespaceMode is enabled due to missing authentication on specific RPCs.","url":"https://insights.sbomify.com/CVE-2026-53714/"}