Skip to main content
Vulnerability Database/CVE-2026-93540

CVE-2026-93540: SUSE Rancher Fleet Privilege Escalation

CVE-2026-93540 is a privilege escalation vulnerability in SUSE Rancher Fleet allowing unauthorized namespace metadata modification. This article covers technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-93540 Overview

CVE-2026-93540 is a privilege mismatch vulnerability in SUSE Rancher Fleet, a GitOps-based continuous delivery tool for Kubernetes clusters. When a bundle requests namespace labels or annotations through the namespaceLabels and namespaceAnnotations options, the resulting namespace metadata update is not subject to the same authorization checks as the rest of the bundle's deployment. An authenticated user can modify labels and annotations on a target namespace even when the bundle's pinned identity lacks authorization to modify that namespace. This flaw is tracked under [CWE-266: Incorrect Privilege Assignment].

Critical Impact

An authenticated attacker with bundle creation privileges can tamper with namespace metadata outside their authorization scope, potentially disrupting workload scheduling, admission control, and policy enforcement.

Affected Products

  • SUSE Rancher Fleet 0.16 before 0.16.2
  • SUSE Rancher Fleet 0.15 before 0.15.7, 0.14 before 0.14.11
  • SUSE Rancher Fleet 0.13 before 0.13.16 and potentially older versions

Discovery Timeline

  • 2026-09-28 - CVE-2026-93540 published to NVD
  • 2026-09-29 - Last updated in NVD database

Technical Details for CVE-2026-93540

Vulnerability Analysis

Fleet deploys Kubernetes resources through bundles that are pinned to a service identity. The identity's permissions determine what resources the bundle may create or modify within target clusters. The namespaceLabels and namespaceAnnotations bundle options allow a bundle to attach metadata to the namespace in which its resources are deployed. The authorization logic that enforces identity-scoped permissions for standard bundle resources is not applied to this metadata update path. A bundle can therefore mutate labels and annotations on a target namespace even when the pinned identity lacks patch or update rights on that namespace object. This creates a disconnect between the declared authorization boundary and the effective privileges a bundle holds at runtime.

Root Cause

The root cause is a missing authorization check in the namespace metadata reconciliation path. Fleet applies namespaceLabels and namespaceAnnotations using controller-level privileges rather than evaluating the pinned identity's RBAC permissions against the target namespace. This is a classic incorrect privilege assignment pattern where one code path bypasses the authorization model enforced elsewhere in the system.

Attack Vector

An attacker needs authenticated access with permission to create or modify Fleet bundles. The attacker crafts a bundle targeting a namespace outside their authorization scope and populates the namespaceLabels or namespaceAnnotations fields with chosen values. When Fleet reconciles the bundle, the controller writes the attacker-controlled metadata to the target namespace without validating the pinned identity's permissions. The attacker can overwrite labels used by network policies, admission webhooks, pod scheduling selectors, or Open Policy Agent rules, altering security posture across tenant boundaries.

No verified exploitation code is published. Refer to the GitHub Security Advisory GHSA-m93g-8438-2cgg for vendor technical details.

Detection Methods for CVE-2026-93540

Indicators of Compromise

  • Unexpected changes to metadata.labels or metadata.annotations on Kubernetes namespaces that correlate with Fleet bundle reconciliation events.
  • Fleet BundleDeployment objects containing namespaceLabels or namespaceAnnotations entries that reference namespaces outside the bundle owner's authorization scope.
  • Kubernetes audit log entries showing namespace patch or update operations by the Fleet controller service account targeting namespaces owned by other tenants.

Detection Strategies

  • Enable Kubernetes API server audit logging and alert on patch and update verbs against the namespaces resource performed by the Fleet controller service account.
  • Review GitOps repositories and BundleDeployment manifests for use of namespaceLabels and namespaceAnnotations and validate that each use aligns with the pinned identity's RBAC.
  • Compare the current state of namespace labels and annotations against the declared state in authoritative GitOps repositories to detect drift.

Monitoring Recommendations

  • Ingest Kubernetes audit logs and Fleet controller logs into a centralized data lake for correlation and retention.
  • Create alerts for cross-tenant namespace modifications and for bundles that modify namespaces outside their project scope.
  • Monitor admission controller decisions for sudden changes driven by label or annotation mutations on namespaces hosting sensitive workloads.

How to Mitigate CVE-2026-93540

Immediate Actions Required

  • Upgrade Fleet to a patched release: 0.16.2, 0.15.7, 0.14.11, or 0.13.16 depending on your deployed minor version.
  • Audit existing BundleDeployment resources for use of namespaceLabels and namespaceAnnotations and remove unauthorized entries.
  • Review namespace label and annotation history on sensitive namespaces for signs of unauthorized modification.

Patch Information

SUSE has released fixed versions of Rancher Fleet that enforce authorization on the namespace metadata update path. Upgrade to Fleet 0.16.2, 0.15.7, 0.14.11, or 0.13.16 or later. Full remediation details are documented in the GitHub Security Advisory GHSA-m93g-8438-2cgg.

Workarounds

  • Restrict bundle creation and modification privileges to trusted operators using Fleet's role bindings and Rancher project RBAC.
  • Enforce admission policies (OPA Gatekeeper, Kyverno) that prevent unauthorized modification of labels and annotations on sensitive namespaces.
  • Where upgrades cannot be applied immediately, avoid using namespaceLabels and namespaceAnnotations in bundles that target multi-tenant clusters.
bash
# Configuration example: upgrade Fleet via Helm to a patched release
helm repo update
helm upgrade fleet fleet/fleet \
  --namespace cattle-fleet-system \
  --version 0.16.2

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.