Skip to main content
Menu
CVEs

CVE

Red Hat Multicluster Engine for Kubernetes cross-tenant secret access in Hive ClusterClaim controller

CVE-2026-120472EUVD-2026-128414GHSA-X2QR-3J78-F43FPublished Updated Summary written by a model

5.9MediumCNA
Exploited
No known exploitation
Fix
See vendor advisory
Who is exposed
Not reported

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.

Original 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.

cve.now Index

25Pcve.now Index 25 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach10/20Shipped in major Linux distributions
  • Severity6.9/10CVSS 5.9, total technical impact per CISA
  • No patch5/5No fixed version listed; see vendor advisory

What would change the score

  • Would score about 80 if added to CISA KEV
  • Would score about 75 if CISA's SSVC rates exploitation active
  • Would score about 44 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

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"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  4. Record last updated

Affected versions

  • multicluster-engine/hive-rhel9

    Version range not reported

Evidence 6

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

More CVEs