github.com/kgateway-dev/kgateway/v2
Affected
- introduced
2.1.0-agw-cel-rbac, fixed2.1.0(semver)
Fixed versions
2.1.0
Fix
- Fixed version
2.1.0go get github.com/kgateway-dev/kgateway/[email protected]
Advisory
Also known as: CVE-2025-64323, GO-2025-4094
kgateway is missing xDS authorization
Summary
The xDS interface in Kgateway versions 2.0.0 through 2.0.4 lacks 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.
Description
Impact
Kgateway xDS interface did not have authorization, so anonymous clients with unrestricted network access could gain access to the xDS data. This could expose sensitive information about your gateway configuration, certificate data, backend services, and routing topology to unauthorized parties.
Patches
Upgrade to version 2.0.5 or 2.1.0. These versions enable JWT-based authentication for the xDS interface by default, ensuring that only authenticated clients can access the xDS configuration data.
Workarounds
If immediate upgrade is not possible, NetworkPolicies can be used to block access to kgateway's xDS port, restricting network access to only trusted sources.
References
Credits
Kindly reported by @rikatz
For More Information
If you have any questions or comments about this advisory, please reach out in slack https://cloud-native.slack.com/archives/C080D3PJMS4
Medium Basis: The source's own band: MODERATE
2.1.0-agw-cel-rbac, fixed 2.1.0 (semver)2.1.0
2.1.0go get github.com/kgateway-dev/kgateway/[email protected]0, fixed 2.0.5 (semver)2.0.5
2.0.5go get github.com/kgateway-dev/kgateway/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0