Rancher's Azure AD permission changes are not reflected on active sessions
Published 3 Mar 2026 · Updated 8 Jul 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.7 <2.6.13
- Fixed in
- 2.6.13
go get github.com/rancher/rancher@v2.6.13- Affected
- >=2.7.0 <2.7.4
- Fixed in
- 2.7.4
go get github.com/rancher/rancher@v2.7.4Details
A bug has been identified in which permission changes in Azure AD are not reflected to users while they are logged in the Rancher UI. This would cause the users to retain their previous permissions in Rancher, even if they change groups on Azure AD, for example, to a lower privileged group, or are removed from a group, thus retaining their access to Rancher instead of losing it.
Impact
This issue only affects Rancher instances with Azure AD integration enabled, regardless of the automatically refreshing settings which are enabled by default. The users that obtained a token (or kubeconfig) to access Rancher through the following sessions are affected by this issue:
1) Users using the Rancher UI.
2) Users using kubectl based on a kubeconfig downloaded through the Rancher UI.
3) Tokens created via the Rancher UI Create API Key feature.
Note that the permission caching is persisted even when the Rancher Manager pod is restarted. The only way for a user to get the new permissions is to logout and login again.
Patches
Patched versions include releases 2.6.13, 2.7.4 and later versions.
For more information
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-vf6j-6739-78m8 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.