# CVE-2026-10101: Assisted-service: assisted-service: infraenv status leaks referenced pull-secret contents to namespace view users

> Assisted-service leaks pull-secret contents in InfraEnv status, allowing namespace viewers to bypass RBAC and read sensitive credentials.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 29 May 2026
- **Updated:** 2 Jul 2026
- **Also known as:** GHSA-jxxw-7x7w-4x47

## What is CVE-2026-10101?

CVE-2026-10101 is a medium-severity vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 29 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official 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`.

Weakness: CWE-201 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-10101?


## How do I fix CVE-2026-10101?

No fix has been published for CVE-2026-10101 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10101 being exploited?

There is no known exploitation of CVE-2026-10101 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10101 and fix it if it is affected.

What it is: CVE-2026-10101 is a medium-severity vulnerability in Red Hat Multicluster Engine for Kubernetes, published on 29 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-10101 in the wild and no public exploit code.

Affected product: Red Hat Multicluster Engine for Kubernetes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-10101/ (Markdown: https://insights.sbomify.com/CVE-2026-10101/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-10101
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-10101
- OSV: https://osv.dev/vulnerability/CVE-2026-10101

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-10101/
Summaries are generated and may contain mistakes; the official description above is the record.