1-minute read of a 4 min report

IBM Turbonomic Operator Grants Cluster-Wide Access to Secrets

By

1-minute read

What a defender needs to know

IBM Turbonomic’s Prometurbo operator had a service account with cluster-wide get, list and watch permission on Kubernetes secrets, Unit 42 researcher Lior Yakim found. If an attacker compromises that operator or its account, it can reach credentials in namespaces unrelated to the operator’s job. IBM’s CVE-2026-6389 record lists Prometurbo 8.16.0 through 8.17.6 as affected and directs operators to reinstall a version with fixes, naming 8.18.0.

Check the installed Prometurbo agent version and its deployed ClusterRoleBindings and RoleBindings. After reinstalling the fixed agent, ask the Kubernetes API server whether the operator’s service account can list secrets across namespaces and get secrets in an unrelated namespace, using kubectl auth can-i with administrator-authorized impersonation. For a namespace-scoped operator, expect no outside its intended scope while its own reconciliation continues. Review other installed operators against their documented jobs before narrowing bindings; Datadog explained to Unit 42 that its dynamic secret names require different operational considerations.

Unit 42 advises watching Kubernetes audit events for operator accounts listing secrets outside their working namespace or contacting the API server from an unexpected address. Such events help investigate activity, while the effective-permission test answers whether an unused broad grant remains. Unit 42 documents a permission an attacker could use after compromising the operator; it reports no Prometurbo intrusion.

Primary sources