github.com/rancher/fleet
Affected
- introduced
0.15.0, fixed0.15.1(semver)
Fixed versions
0.15.1
Fix
- Fixed version
0.15.1go get github.com/rancher/[email protected]
Advisory
Also known as: CVE-2026-41050, GO-2026-5207
Fleet: Helm impersonation bypass of RESTClientGetter retains cluster-admin during template rendering
Impact
Fleet's Helm deployer did not fully apply ServiceAccount impersonation in two code paths, allowing a tenant with git push access to a Fleet-monitored repository to read secrets from any namespace on every downstream cluster targeted by their GitRepo.
Helm `lookup` bypass: The Helm template engine ran Kubernetes API queries with the fleet-agent's cluster-admin credentials instead of the impersonated ServiceAccount. A chart template could therefore access resources beyond the tenant's RBAC scope.
`valuesFrom` bypass: Secret and ConfigMap references in fleet.yaml helm.valuesFrom were read using the fleet-agent's cluster-admin client. A tenant could reference resources in namespaces the impersonated ServiceAccount has no access to.
Both issues break Fleet's multi-tenant impersonation boundary. The leaked credentials may belong to external services, making the full impact non-deterministic.
Single-tenant deployments where all users are trusted are not affected.
Important:
Please consult the associated MITRE ATT&CK - Technique - Account Access Removal for further information about this category of attack.
Patches
Both issues are fixed by ensuring the Helm action configuration consistently uses the impersonated ServiceAccount credentials throughout all Helm operations.
Patched versions of Rancher include releases v2.14.1, v2.13.5, v2.12.9, and v2.11.13. For Rancher v2.10.11, users must manually update their Fleet deployment to versionv0.11.13.
Workarounds
No workaround fully mitigates the issue for multi-tenant deployments. The patches should be applied as soon as they are available.
The following measures reduce the attack surface but do not close either vulnerability:
GitRepoRestriction resources to limit which ServiceAccounts each namespace is allowed to use, restricting the set of users who can configure impersonation at all.lookup calls and fleet.yaml files for cross-namespace valuesFrom references as a detective control.Resources
If there are any questions or comments about this advisory:
Critical Basis: The source's own band: CRITICAL
0.15.0, fixed 0.15.1 (semver)0.15.1
0.15.1go get github.com/rancher/[email protected]0.14.0, fixed 0.14.5 (semver)0.14.5
0.14.5go get github.com/rancher/[email protected]0.13.0, fixed 0.13.10 (semver)0.13.10
0.13.10go get github.com/rancher/[email protected]0.12.0, fixed 0.12.14 (semver)0.12.14
0.12.14go get github.com/rancher/[email protected]0.11.0, fixed 0.11.13 (semver)0.11.13
0.11.13go 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