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.
Statement
Red Hat rates this flaw as Moderate impact. Exploitation requires a namespace "view" user to be in a namespace where an InfraEnv references a pull secret that fails assisted-service validation -- a condition the "view" user cannot trigger themselves. Red Hat scores UI:R (User Interaction Required) because the leak only exists when an administrator creates or updates an InfraEnv referencing a pull secret that fails validation; without that admin action, there is nothing to exploit. The direct impact is confidentiality: the full pull-secret content is disclosed through InfraEnv status, bypassing the Kubernetes RBAC boundary that prevents "view" users from reading Secrets. Red Hat scores I:L (Integrity: Low) rather than I:H because, with Scope: Unchanged, integrity impact should reflect the vulnerable component (MCE/ACM), not external registries. The leaked credential's write capability is conditional on the specific credential's permissions and does not represent integrity compromise of the ACM/MCE cluster itself.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.3 | N/A | 6.3 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | Low | N/A | Low |
| Privileges Required | Low | N/A | Low |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | Low | N/A | Low |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N
cve.org: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Files or Directories; Read Memory; Read Application Data
Sensitive data may be exposed to attackers.
Acknowledgements
Red Hat would like to thank Christopher Lusk (North Echo Security Research) for reporting this issue.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
