CVE-2026-10101
Description
ACM/MCE assisted-service writes raw referenced pull-secret contents into InfraEnv.status.conditions[].message when pull-secret validation fails. A namespace principal with the stock view ClusterRole cannot directly read Secrets, but can read InfraEnv objects and recover the referenced Secret's .dockerconfigjson data from status.
This bypasses the Kubernetes/OpenShift RBAC separation between read-only namespace viewers and Secret readers. In the reproduced proof, the same ServiceAccount was denied get and list on Secrets, but recovered synthetic pull-secret username, password, email, and base64 auth fields through InfraEnv.status.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
ACM/MCE assisted-service leaks pull-secret contents into InfraEnv status, allowing namespace viewers to bypass RBAC and recover secret data.
Vulnerability
In ACM/MCE assisted-service, when pull-secret validation fails, the raw contents of the referenced pull-secret are written into InfraEnv.status.conditions[].message. This occurs because the service copies the .dockerconfigjson data directly into the status field without sanitization. The vulnerability affects versions of ACM/MCE assisted-service prior to a fix (specific versions not disclosed in the available references) [1][2].
Exploitation
An attacker with a namespace principal that has the stock view ClusterRole (or equivalent read-only access) cannot directly read Secrets via the Kubernetes API. However, they can read InfraEnv objects. By creating or modifying an InfraEnv resource that references a pull-secret and triggering a validation failure (e.g., by providing an invalid pull-secret reference), the attacker can then read InfraEnv.status.conditions[].message to recover the secret's .dockerconfigjson data, including username, password, email, and base64 auth fields [1][2].
Impact
Successful exploitation allows an attacker to bypass the RBAC separation between read-only namespace viewers and Secret readers. The attacker gains unauthorized access to pull-secret credentials, which may be used to authenticate to container registries or other services. This can lead to privilege escalation or lateral movement within the cluster if the pull-secret has broader access [1][2].
Mitigation
No fix has been disclosed in the available references. Users should restrict access to InfraEnv objects to trusted principals only, and avoid referencing pull-secrets that contain sensitive credentials in environments where untrusted users have view access. Monitor Red Hat advisories for a patched version [1][2].
AI Insight generated on May 29, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
2News mentions
0No linked articles in our index yet.