The vulnerability occurs because the ACM/MCE assisted-service writes raw referenced pull-secret contents into the InfraEnv.status.conditions[].message field upon pull-secret validation failure. Although a namespace principal with the default 'view' ClusterRole cannot directly read Kubernetes Secrets, it can read InfraEnv objects and extract the referenced Secret's .dockerconfigjson data from the status field. This effectively bypasses the intended RBAC separation between read-only namespace viewers and Secret readers. Proof of concept shows that a ServiceAccount denied 'get' and 'list' permissions on Secrets can still recover sensitive pull-secret fields such as username, password, email, and base64 auth data via InfraEnv.status.

An attacker with read access to InfraEnv objects but without direct Secret read permissions can obtain sensitive authentication credentials stored in pull-secrets. This compromises confidentiality of secret data, potentially allowing unauthorized access to container registries or other resources protected by these credentials. The integrity and availability impacts are low, but the confidentiality impact is high.

Patch status is not yet confirmed — check the Red Hat advisory at https://access.redhat.com/security/cve/CVE-2026-10101 for current remediation guidance. Until a fix is available, restrict access to InfraEnv objects to trusted principals only, as the vulnerability allows leakage of secret data through InfraEnv.status fields. Monitor vendor updates for official fixes or workarounds.