What is GHSA-5PMX-7R6R-WFQQ?

GHSA-5PMX-7R6R-WFQQ is a medium-severity path traversal vulnerability in github.com/kgateway-dev/kgateway/v2 (go), affecting versions < 2.0.5. It is fixed in 2.0.5, 2.1.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.

How severe is GHSA-5PMX-7R6R-WFQQ?

GHSA-5PMX-7R6R-WFQQ has a CVSS score of 6.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 GHSA-5PMX-7R6R-WFQQ?

github.com/kgateway-dev/kgateway/v2 (go) versions < 2.0.5 is affected.

Is there a fix for GHSA-5PMX-7R6R-WFQQ?

Yes. GHSA-5PMX-7R6R-WFQQ is fixed in 2.0.5, 2.1.0. Upgrade to this version or later.

Is GHSA-5PMX-7R6R-WFQQ exploitable, and should I be worried?

Whether GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ?

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

GHSA-5PMX-7R6R-WFQQ in github.com/kgateway-dev/kgateway/v2 | Intelligent Application Security

Q: How severe is GHSA-5PMX-7R6R-WFQQ?

GHSA-5PMX-7R6R-WFQQ has a CVSS score of 6.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 GHSA-5PMX-7R6R-WFQQ?

github.com/kgateway-dev/kgateway/v2 (go) versions < 2.0.5 is affected.

Q: Is there a fix for GHSA-5PMX-7R6R-WFQQ?

Yes. GHSA-5PMX-7R6R-WFQQ is fixed in 2.0.5, 2.1.0. Upgrade to this version or later.

Q: Is GHSA-5PMX-7R6R-WFQQ exploitable, and should I be worried?

Whether GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ?

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

Summary

The transformation policy template feature in Kgateway versions through 2.0.4 allows users with TrafficPolicy creation permissions to craft transformations that read and expose arbitrary files from the dataplane container filesystem.

Description

Workarounds

If you are not using transformations, you can disallow TrafficPolicy creation or restrict transformation usage using a ValidatingAdmissionPolicy to prevent exploitation while preparing to upgrade.

References

Fix in 2.1.0: https://github.com/kgateway-dev/kgateway/pull/12528 (envoy-gloo v1.35.2-patch4)
Backport to 2.0.5: Included in https://github.com/kgateway-dev/kgateway/pull/12535 (envoy-gloo v1.34.6-patch3)
Envoy-gloo releases: https://github.com/solo-io/envoy-gloo/releases/tag/v1.35.2-patch4
Envoy-gloo releases: https://github.com/solo-io/envoy-gloo/releases/tag/v1.34.6-patch3

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

Users with permissions to create a TrafficPolicy can create a transformation that returns files from within the dataplane container. While no secrets are mounted to the container by default, users who mount custom volumes to the dataplane should be aware of potential data exposure through this vulnerability.

This could allow unauthorized access to:

Configuration files within the container
Custom mounted volumes and their contents
Any files accessible to the dataplane container process

Note: Updated availability score to high, as under some configurations this can prevent xDS updates.

Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.

GHSA-5PMX-7R6R-WFQQ has a CVSS score of 6.3 (Medium). The vector is reachable from an adjacent network, low 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.0.5, 2.1.0); upgrading removes the vulnerable code path.

Affected versions

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

Security releases

github.com/kgateway-dev/kgateway/v2 → 2.0.5 (go) github.com/kgateway-dev/kgateway/v2 → 2.1.0 (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 include an updated transformation filter in envoy-gloo that prevents file access through transformation templates.

Frequently Asked Questions

What is GHSA-5PMX-7R6R-WFQQ? GHSA-5PMX-7R6R-WFQQ is a medium-severity path traversal vulnerability in github.com/kgateway-dev/kgateway/v2 (go), affecting versions < 2.0.5. It is fixed in 2.0.5, 2.1.0. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
How severe is GHSA-5PMX-7R6R-WFQQ? GHSA-5PMX-7R6R-WFQQ has a CVSS score of 6.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 GHSA-5PMX-7R6R-WFQQ? github.com/kgateway-dev/kgateway/v2 (go) versions < 2.0.5 is affected.
Is there a fix for GHSA-5PMX-7R6R-WFQQ? Yes. GHSA-5PMX-7R6R-WFQQ is fixed in 2.0.5, 2.1.0. Upgrade to this version or later.
Is GHSA-5PMX-7R6R-WFQQ exploitable, and should I be worried? Whether GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ 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 GHSA-5PMX-7R6R-WFQQ?
- Upgrade github.com/kgateway-dev/kgateway/v2 to 2.0.5 or later
- Upgrade github.com/kgateway-dev/kgateway/v2 to 2.1.0 or later

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

CVE-2025-64323