CVE-2025-64323GO-2025-4094GHSA-4766-X535-JW3R
kgateway is missing xDS authorization
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.1.0, 2.0.5
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
kgateway is a Cloud-Native API and AI Gateway. Versions 2.0.4 and below and 2.1.0-agw-cel-rbac through 2.1.0-rc.2 lack authentication, allowing any client with unrestricted network access to the xDS port to retrieve potentially sensitive configuration data including certificate data, backend service information, routing rules, and cluster metadata. This issue is solved in versions 2.0.5 and 2.1.0.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- kgateway-dev kgateway
From 2.1.0-agw-cel-rbac · fixed in 2.1.0; fixed in 2.0.5
- github.com/kgateway-dev/kgatewayGo
All versions
- github.com/kgateway-dev/kgateway/v2Go
fixed in 2.0.5; From 2.1.0-agw-cel-rbac · fixed in 2.1.0
- github.com/kgateway-dev/kgateway/v2Go
From 2.1.0-agw-cel-rbac · fixed in 2.1.0
- github.com/kgateway-dev/kgateway/v2Go
fixed in 2.0.5