kgateway is missing xDS authorization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.3 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS

• CVE-2025-64323: 0.16% estimated exploitation activity in the next 30 days; percentile 5.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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.…

Published by the source

4 Nov 2025, 18:39 UTC

Last modified by the source

7 Nov 2025, 16:42 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-4766-x535-jw3r

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-64323

Advisory: kgateway is missing xDS authorization
IDs: CVE-2025-64323, GHSA-4766-x535-jw3r
Record: https://patchnext.com/advisories/cve-2025-64323 (revision 1, source checked 26 Oct 2026, 15:13 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/kgateway-dev/kgateway/v2 2.1.0, 2.0.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/kgateway-dev/kgateway/v2: affected >= 2.1.0-agw-cel-rbac, < 2.1.0; < 2.0.5; fixed in 2.0.5, 2.1.0

## Suggested inspection (read-only)
- Go github.com/kgateway-dev/kgateway/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/kgateway-dev/kgateway/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-4766-x535-jw3r (GitHub-reviewed advisory GHSA-4766-x535-jw3r lists affected ranges: Go github.com/kgateway-dev/kgateway/v2 >=2.1.0-agw-cel-rbac =0 <2.0.5)

Commands are suggestions: review each one before running it.