Kgateway transformation policy template can emit files from the container

Exploitation

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

CVSS

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

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

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 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. Patches Upgrade to version 2.0.5 or 2.1.0. These versions include an updated transformation filter in envoy-gloo that prevents file access…

Published by the source

4 Nov 2025, 18:58 UTC

Last modified by the source

17 Nov 2025, 17:49 UTC

Source last checked

26 Oct 2026, 15:13 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-5pmx-7r6r-wfqq

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

# Patch Next advisory brief: GHSA-5pmx-7r6r-wfqq

Advisory: Kgateway transformation policy template can emit files from the container
IDs: GHSA-5pmx-7r6r-wfqq
Record: https://patchnext.com/advisories/ghsa-5pmx-7r6r-wfqq (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 6.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.0.5; >= 2.1.0-agw-cel-rbac, < 2.1.0; 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-5pmx-7r6r-wfqq (GitHub-reviewed advisory GHSA-5pmx-7r6r-wfqq lists affected ranges: Go github.com/kgateway-dev/kgateway/v2 >=0 =2.1.0-agw-cel-rbac <2.1.0)

Commands are suggestions: review each one before running it.