<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: SUSE Rancher</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/suse-rancher.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-88811: Rancher credentials disclosed to third-party hosts by the Rancher Manager meta proxy</title><link>https://vulnfeed.org/cve/CVE-2026-88811/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-88811/</guid><pubDate>Mon, 02 Nov 2026 16:48:44 +0000</pubDate><description>Missing filtering in the SUSE Rancher Manager meta proxy could cause passed in rancher credentials to be leaked to cloud providers. This affects SUSE Rancher 2.15.0 up to 2.15.3, 2.14.0 up to 2.14.7, 2.13.0 up to 2.13.11,</description></item><item><title>CVE-2026-88810: Privilege escalation in downstream clusters via GlobalRole inheritedNamespacedRules</title><link>https://vulnfeed.org/cve/CVE-2026-88810/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-88810/</guid><pubDate>Mon, 02 Nov 2026 16:29:46 +0000</pubDate><description>A privilege escalation issue was discovered in Rancher Manager&apos;s role-based access control. The inheritedNamespacedRules field of a GlobalRole propagates permissions into named namespaces of every downstream cluster managed by the Rancher instance, but it was not subject to the privilege-escalation validation applied to the other permission-carrying fields of a GlobalRole. As a result, a non-administrative user could be granted, through a global role binding, permissions in downstream clusters that exceed the permissions that user already holds. This affected SUSE Rancher 2.15.2 only, and SUSE Rancher Webhook 0.11.0 up to 0.11.4, and 0.12.0 up to 0.12.1.</description></item><item><title>CVE-2026-94290: Privilege escalation to cluster-admin on the Rancher local cluster through Fleet&apos;s agent management controller</title><link>https://vulnfeed.org/cve/CVE-2026-94290/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-94290/</guid><pubDate>Mon, 02 Nov 2026 16:17:45 +0000</pubDate><description>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&apos;s behalf and to run that user&apos;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></item><item><title>CVE-2026-88809: Rancher meta proxy allowlist bypass leading to server-side request forgery</title><link>https://vulnfeed.org/cve/CVE-2026-88809/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-88809/</guid><pubDate>Mon, 02 Nov 2026 16:03:20 +0000</pubDate><description>A security vulnerability exists in the SUSE Rancher Manager meta proxy endpoint (/meta/proxy). This endpoint is intended to forward requests only to destinations that appear on a configured allowlist. The allowlist decision was evaluated in a place where it could not stop a request from being forwarded, so a rejected destination was logged but the request was still handed to the proxy&apos;s transport. This affects SUSE Rancher 2.15.0 up to 2.15.3, 2.14.0 up to 2.14.7, 2.13.0 up to 2.13.11, 2.12.0 up to 2.12.15, 2.11.0 up to 2.11.19 and potentially older EOL versions.</description></item></channel></rss>
