Rancher permissions on 'namespaces' in any API group grants 'edit' permissions on namespaces in 'core'
Published 8 Feb 2024 · Updated 10 Sept 2026
Is your project on an affected github.com/rancher/rancher?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- >=2.6.0 <2.6.14
- Fixed in
- 2.6.14
go get github.com/rancher/rancher@v2.6.14- Affected
- >=2.7.0 <2.7.10
- Fixed in
- 2.7.10
go get github.com/rancher/rancher@v2.7.10- Affected
- >=2.8.0 <2.8.2
- Fixed in
- 2.8.2
go get github.com/rancher/rancher@v2.8.2Details
Impact
A vulnerability has been identified when granting a create or * global role for a resource type of "namespaces"; no matter the API group, the subject will receive * permissions for core namespaces. This can lead to someone being capable of accessing, creating, updating, or deleting a namespace in the project. This includes reading or updating a namespace in the project so that it is available in other projects in which the user has the "manage-namespaces" permission or updating another namespace in which the user has normal "update" permissions to be moved into the project.
The expected behavior is to not be able to create, update, or delete a namespace in the project or move another namespace into the project since the user doesn't have any permissions on namespaces in the core API group.
Moving a namespace to another project could lead to leakage of secrets, in case the targeted project has secrets. And also can lead to the namespace being able to abuse the resource quotas of the targeted project.
Patches
Patched versions include releases 2.6.14, 2.7.10 and 2.8.2.
Workarounds
There is no direct mitigation besides updating Rancher to a patched version.
References
If you have any questions or comments about this advisory:
- Reach out to the SUSE Rancher Security team for security-related inquiries.
- Open an issue in the Rancher repository.
- Verify with our support matrix and product support lifecycle.
Is GHSA-c85r-fwc7-45vc in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/rancher/rancher, and gives you the command that fixes it.
More advisories for github.com/rancher/rancher
- LowCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider in github.com/rancher/rancher · 7 Jul 2026
- LowCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter in github.com/rancher/rancher · 7 Jul 2026
- LowCVE-2026-41052Rancher has Privilege Escalation from Project Owner to Host in github.com/rancher/rancher · 7 Jul 2026
- CriticalCVE-2026-41052Rancher has Privilege Escalation from Project Owner to Host · 1 Jul 2026
- HighCVE-2026-41053Rancher has over-inclusive team membership expansion in GitHub App authentication provider · 1 Jul 2026
- CriticalCVE-2026-44939Rancher vulnerable to command injection through unsanitized YAML parameter · 1 Jul 2026
References
- Linkgithub.com/rancher/rancher/security/advisories/GHSA-c85r-fwc7-45vc
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-32194
- Linkgithub.com/rancher/rancher/commit/2f7113dc32d4f1f5375a1ae09b65be58f6801a15
- Linkgithub.com/rancher/rancher/commit/649fdad268d8ecc748e9fdcca2ddcfdc900f9eaa
- Linkgithub.com/rancher/rancher/commit/d4a0ff5e779e3cc5f14d77ce57620e1326ab1c22
- Linkbugzilla.suse.com/show_bug.cgi?id=CVE-2023-32194
- Packagegithub.com/rancher/rancher
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.