NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · Go

CVE-2023-22648: Rancher's Azure AD permission changes are not reflected on active sessions

highCVSS 3.1 8.0GHSA-vf6j-6739-78m8

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.

Published Mar 3, 2026

Affected packages

github.com/rancher/rancher

Ecosystem
Go
Affected
>= 2.6.7, < 2.6.13
Fixed in
2.6.13
Check
go list -m github.com/rancher/rancher

github.com/rancher/rancher

Ecosystem
Go
Affected
>= 2.7.0, < 2.7.4
Fixed in
2.7.4
Check
go list -m github.com/rancher/rancher

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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:

Credited to yvespp.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More Go vulnerabilities

All Go entries