github.com/rancher/fleet
Affected
- introduced
0.15.0, fixed0.15.2(semver)
Fixed versions
0.15.2
Fix
- Fixed version
0.15.2go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2026-44938, GO-2026-5871
Fleet has PSS Bypass through addLabelsFromOptions in Fleet Agent
Impact
A vulnerability has been identified in Fleet's agent-side deployer, which did not filter security-sensitive keys from namespaceLabels in fleet.yaml (or BundleDeployment.spec.options.namespaceLabels) when applying them to the target namespace.
An attacker with git push access to a Fleet-monitored repository could overwrite Pod Security Standards (PSS) enforcement labels on a target namespace. This allows the attacker to weaken admission controls and deploy workloads that PSS policies would otherwise block.
Important: The final impact on confidentiality, integrity, and availability depends on the specific permissions of the leaked credentials.
Fleet team recommends you:
Please consult the associated MITRE ATT&CK - Technique - Disable or Modify Tools for further information about this category of attack.
Patches
To fix this issue, upgrade to a patched version. The updated Fleet deployer filters out labels with the pod-security.kubernetes.io/ prefix when applying namespaceLabels to a namespace. This change preserves the PSS labels set by cluster administrators and prevents them from being overwritten through fleet.yaml or BundleDeployment options.
Patched versions of Fleet include releases v0.15.2, v0.14.6, v0.13.11, and v0.12.15.
Workarounds
If you can’t immediately upgrade to a patched version, use one of the following workarounds:
1 - Deploy NeuVector(primary workaround)
Deploy NeuVector (SUSE Security) and configure an admission control Deny rule for "Run as privileged" in Protect mode.
2 - Restrict repository access (secondary workaround)
Note: The following measure reduces the attack surface but does not close the vulnerability:
Credits
This security issue was reported by the following collaborators according to our responsible disclosure policy:
References
High Basis: The source's own band: HIGH
0.15.0, fixed 0.15.2 (semver)0.15.2
0.15.2go get github.com/rancher/[email protected]0.14.0, fixed 0.14.6 (semver)0.14.6
0.14.6go get github.com/rancher/[email protected]0.13.0, fixed 0.13.11 (semver)0.13.11
0.13.11go get github.com/rancher/[email protected]0.12.0, fixed 0.12.15 (semver)0.12.15
0.12.15go get github.com/rancher/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0