Skip to content
statance
MenuClose
critical · CVSS 9.1

CVE-2026-94290

Privilege escalation to cluster-admin on the Rancher local cluster through Fleet's agent management controller

Published 2 Nov 2026 · Source updated 3 Nov 2026 · Retrieved 2026-11-04 11:51 UTC · This record may be stale; verify the source

Statance checks for CVE-2026-94290. Running containers on connected servers and Kubernetes nodes are checked for affected image releases, judged on the image tag. Check my servers ↗
Monitor this CVE ↗Full CVE monitoring on Pro and Business

What happened?

SUSE Rancher Fleet clusters reference a kubeconfig secret that the controller uses to install and manage a Fleet agent on the target cluster. The controller did not sufficiently restrict which kubeconfig secrets a Fleet Cluster object was allowed to reference. As a result, a Fleet cluster defined in a namespace an ordinary user controls could be associated with administrative credentials for the management cluster itself, causing the controller to manage the management cluster on that user's behalf and to run that user's Fleet content there with elevated privileges. This affects SUSE Rancher Fleet 0.16.0 up to 0.16.3, 0.15.0 up to 0.15.8, 0.14.0 up to 0.14.12, 0.13.0 up to 0.13.17 and possible older versions.

Description supplied by CVE Program. Formatting is simplified; follow the original advisory for full details.

Affected software and versions

Source-provided software and version information
SoftwareVersion informationFixed version
FleetSUSEaffected: 0.16.0 to < 0.16.3; affected: 0.15.0 to < 0.15.8; affected: 0.14.0 to < 0.14.12; affected: 0.13.0 to < 0.13.17See vendor advisory

Version information comes from the source record and can include unaffected products and exceptions. Distribution packages may contain backported fixes: an older upstream version alone does not prove a server is affected.

Is it being exploited?

This CVE was not listed in the CISA catalogue at our last retrieval. This does not establish that exploitation is absent.

CISA data retrieved 2026-11-06 16:38 UTC. Check CISA ↗

How to respond

  1. Confirm the product, installed package version, and any configuration requirements in the vendor advisory.
  2. Follow the vendor’s remediation or workaround guidance in the references below. Structured fixed-version data is unavailable here; the publisher’s description may include a fix or workaround.
  3. Restart affected services if required, then verify the running version. Known exploitation may warrant investigation as well as patching.

Sources and remediation references

This public advisory does not determine whether a particular server is affected. Records are refreshed as sources change; verify urgent decisions against the original advisory.

← Browse the public CVE feed