CVE-2026-93540: Fleet applies namespace labels and annotations without the bundle's service account privileges
A privilege mismatch was found in Fleet. When a bundle requested namespace labels or annotations through the namespaceLabels and namespaceAnnotations options, the resulting namespace metadata update was not subject to the same authorization as the rest of the bundle's deployment. As a result, a bundle could change labels and annotations on a target namespace even when the identity it was pinned to was not authorized to modify that namespace.
This affected SUSE Rancher Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, 0.13 before 0.13.16 and potentially older versions.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.16.2 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.15.7 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.14.11 - Upgrade
Upgrade
SUSE Rancher Fleetto a version that resolves this vulnerability.Fixed in 0.13.16
Event History
Frequently Asked Questions
Which deployments are affected?
Affected releases are SUSE Rancher Fleet 0.16 before 0.16.2, 0.15 before 0.15.7, 0.14 before 0.14.11, and 0.13 before 0.13.16. Potentially older versions may also be affected.
What must an attacker be able to do to exploit this?
An attacker needs privileges to deploy or control a bundle that uses the namespaceLabels or namespaceAnnotations options. The bundle can then update metadata on its target namespace despite the pinned service account lacking authorization to modify that namespace.
Are bundles that do not request namespace metadata changes affected?
The reported authorization mismatch applies specifically to namespace labels and annotations requested through namespaceLabels and namespaceAnnotations. The provided information does not indicate that other bundle deployment operations bypass the pinned service account's authorization.
How can I identify possible exploitation or exposure?
Review bundles using namespaceLabels or namespaceAnnotations, especially where their pinned service accounts do not have permission to update the target namespaces. Review namespace label and annotation changes associated with those bundles for unexpected metadata updates.