What is CVE-2025-64323?

CVE-2025-64323 is a medium-severity missing authorization vulnerability in github.com/kgateway-dev/kgateway/v2 (go), affecting versions >= 2.1.0-agw-cel-rbac, < 2.1.0. It is fixed in 2.1.0, 2.0.5. The application does not perform an authorization check before performing a sensitive operation.

How severe is CVE-2025-64323?

CVE-2025-64323 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of github.com/kgateway-dev/kgateway/v2 are affected by CVE-2025-64323?

github.com/kgateway-dev/kgateway/v2 (go) versions >= 2.1.0-agw-cel-rbac, < 2.1.0 is affected.

Is there a fix for CVE-2025-64323?

Yes. CVE-2025-64323 is fixed in 2.1.0, 2.0.5. Upgrade to this version or later.

Is CVE-2025-64323 exploitable, and should I be worried?

Whether CVE-2025-64323 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-64323 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2025-64323?

Upgrade: github.com/kgateway-dev/kgateway/v2 to 2.1.0 or later, github.com/kgateway-dev/kgateway/v2 to 2.0.5 or later.

CVE-2025-64323 in github.com/kgateway-dev/kgateway/v2 | Intelligent Application Security

Q: How severe is CVE-2025-64323?

CVE-2025-64323 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of github.com/kgateway-dev/kgateway/v2 are affected by CVE-2025-64323?

github.com/kgateway-dev/kgateway/v2 (go) versions >= 2.1.0-agw-cel-rbac, < 2.1.0 is affected.

Q: Is there a fix for CVE-2025-64323?

Yes. CVE-2025-64323 is fixed in 2.1.0, 2.0.5. Upgrade to this version or later.

Q: Is CVE-2025-64323 exploitable, and should I be worried?

Whether CVE-2025-64323 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2025-64323 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2025-64323?

Upgrade: github.com/kgateway-dev/kgateway/v2 to 2.1.0 or later, github.com/kgateway-dev/kgateway/v2 to 2.0.5 or later.

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

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

Fix in 2.1.0: https://github.com/kgateway-dev/kgateway/pull/12471
Backport to 2.0.5: https://github.com/kgateway-dev/kgateway/pull/12535
Related issue: https://github.com/kgateway-dev/kgateway/issues/10651

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

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.

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2025-64323 has a CVSS score of 5.3 (Medium). The vector is reachable from an adjacent network, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.1.0, 2.0.5); upgrading removes the vulnerable code path.

Affected versions

github.com/kgateway-dev/kgateway/v2 (>= 2.1.0-agw-cel-rbac, < 2.1.0) github.com/kgateway-dev/kgateway/v2 (< 2.0.5)

Security releases

github.com/kgateway-dev/kgateway/v2 → 2.1.0 (go) github.com/kgateway-dev/kgateway/v2 → 2.0.5 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

See it in your environment

Remediation advice

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.

Frequently Asked Questions

What is CVE-2025-64323? CVE-2025-64323 is a medium-severity missing authorization vulnerability in github.com/kgateway-dev/kgateway/v2 (go), affecting versions >= 2.1.0-agw-cel-rbac, < 2.1.0. It is fixed in 2.1.0, 2.0.5. The application does not perform an authorization check before performing a sensitive operation.
How severe is CVE-2025-64323? CVE-2025-64323 has a CVSS score of 5.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of github.com/kgateway-dev/kgateway/v2 are affected by CVE-2025-64323? github.com/kgateway-dev/kgateway/v2 (go) versions >= 2.1.0-agw-cel-rbac, < 2.1.0 is affected.
Is there a fix for CVE-2025-64323? Yes. CVE-2025-64323 is fixed in 2.1.0, 2.0.5. Upgrade to this version or later.
Is CVE-2025-64323 exploitable, and should I be worried? Whether CVE-2025-64323 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-64323 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-64323?
- Upgrade github.com/kgateway-dev/kgateway/v2 to 2.1.0 or later
- Upgrade github.com/kgateway-dev/kgateway/v2 to 2.0.5 or later

Other vulnerabilities in github.com/kgateway-dev/kgateway/v2

CVE-2025-64323