Users authorized to list or watch one type of namespaced custom resource cluster-wide can read custom resources of a different type in the same API group without authorization. Clusters are impacted by this vulnerability if all of the following are true: 1. There are 2+ CustomResourceDefinitions sharing the same API group 2. Users have cluster-wide list or watch authorization on one of those custom resources. 3. The same users are not authorized to read another custom resource in the same API group.
https://www.ibm.com/support/pages/node/6844715
https://security.netapp.com/advisory/ntap-20230511-0004/
https://groups.google.com/g/kubernetes-security-announce/c/iUd550j7kjA