Executive brief
A vulnerability in the Fleet deployment tool allows users with access to a connected Git repository to bypass security policies on Kubernetes clusters. By modifying configuration files, an attacker can disable Pod Security Standards (PSS) for specific namespaces. This enables them to deploy unauthorized or malicious workloads that would normally be blocked by the system's security controls.
Technical details
A vulnerability exists in Fleet's agent-side deployer where it fails to filter security-sensitive keys from 'namespaceLabels' in fleet.yaml or BundleDeployment options. An attacker with low-privileged 'git push' access to a Fleet-monitored repository can provide malicious labels that overwrite existing Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls, facilitating the deployment of privileged or otherwise restricted workloads. The issue is addressed in versions 0.15.2, 0.14.6, 0.13.11, and 0.12.15 by filtering out labels with the 'pod-security.kubernetes.io/' prefix.
Affected products
- SUSE Rancher Fleet >= 0.15.0, < 0.15.2; >= 0.14.0, < 0.14.6; >= 0.13.0, < 0.13.11; >= 0.12.0, < 0.12.15
Timeline
- 2026-05-27: disclosed: Initial disclosure in rancher/fleet repository
- 2026-07-01: advisory: GitHub Advisory published
- 2026-07-07: advisory: NVD publication date