Live › vulnerability › CVE-2026-104623
SUSE Rancher Manager has an authorization gap in its local management cluster shell feature, because the access check was not applied to every API route that reaches it. An authenticated user can use an alternate request form to bypass the check and run a pod on the management cluster.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 17:31 UTC. All times on this page are UTC.
Teams running SUSE Rancher Manager in the affected version ranges, where any authenticated user could reach the local management cluster shell. Installations outside the listed ranges are not named in the sources, and the sources do not say whether specific configurations change exposure.
No product ranges from the sources yet.
No fix yet, per the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
A security vulnerability exists in the authorization handling for the local (management) cluster shell feature of SUSE Rancher Manager 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 possible older versions. The authorization check that was introduced to protect this feature was not applied to every API route that can reach it, so an alternative request form reached the shell handler without the access check being evaluated. This could allow any authenticated users to run a pod on the management cluster.
This page as .md · .json · in your agent: get_signal("CVE-2026-104623")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.