<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:webfeeds="http://webfeeds.org/rss/1.0"><channel><title>Cpe:2.3:a:suse:rancher_fleet:*:*:*:*:*:*:*:* - CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/cpes/cpe2.3asuserancher_fleet/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata. Fed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 02 Nov 2026 17:53:51 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/cpes/cpe2.3asuserancher_fleet/feed.xml" rel="self" type="application/rss+xml"/><image><url>https://feed.craftedsignal.io/favicon-32x32.png</url><title>CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/</link><width>32</width><height>32</height></image><webfeeds:icon>https://feed.craftedsignal.io/favicon.svg</webfeeds:icon><item><title>SUSE Rancher Fleet: Privilege Escalation via Unauthorized Kubeconfig Reference (CVE-2026-94290)</title><link>https://feed.craftedsignal.io/briefs/2026-11-suse-rancher-fleet-privesc/</link><pubDate>Mon, 02 Nov 2026 17:53:51 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-11-suse-rancher-fleet-privesc/</guid><description>SUSE Rancher Fleet fails to restrict kubeconfig secret references, allowing a user to associate cluster definitions with management-level administrative credentials and execute arbitrary content with elevated privileges.</description><content:encoded><![CDATA[<p>SUSE Rancher Fleet clusters reference kubeconfig secrets for the deployment and management of agents on target clusters. A vulnerability exists where the controller does not properly validate or restrict which kubeconfig secrets a Fleet Cluster object may reference. An attacker with control over a namespace can configure a Fleet Cluster object to reference administrative kubeconfig secrets belonging to the management cluster. This results in the Fleet controller interacting with the management cluster using these administrative credentials, enabling the attacker to execute arbitrary Fleet content within the management cluster with elevated privileges.</p>
<h2 id="impact">Impact</h2>
<p>Successful exploitation allows for privilege escalation from a namespace-restricted user to administrative control over the management cluster, potentially leading to full cluster compromise.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Upgrade Rancher Fleet to a patched version once available from SUSE.</li>
<li>Audit existing Fleet Cluster objects for suspicious kubeconfig secret references, particularly those pointing to secrets outside of the object's namespace.</li>
<li>Restrict RBAC permissions for creating or modifying Fleet Cluster objects in non-administrative namespaces.</li>
</ul>
]]></content:encoded><category domain="severity">critical</category><category domain="type">advisory</category><category>privilege-escalation</category><category>kubernetes</category><category>cloud</category></item></channel></rss>