CyberSecBulletin
CVE-2026-66792NVD status: Awaiting Analysis

Multicluster Global Hub 1.4.9: Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2026-66792 is a critical-severity incorrect authorization vulnerability in Multicluster Global Hub 1.4.9 from Red Hat, with a CVSS 3.1 base score of 9.9 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.69% chance of exploitation within 30 days, higher than 53% of scored CVEs.

Patch this week

Critical severity: a successful attack would have severe impact.

What to do

  1. Check which version of Multicluster Global Hub 1.4.9 you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatMulticluster Global Hub 1.4.9Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.5.8Not specified in the recordNot stated
Red HatMulticluster Global Hub 1.6.6Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.11Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.13Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.14Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.15Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.16Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2.17Not specified in the recordNot stated
Red HatRed Hat Advanced Cluster Management for Kubernetes 2Not specified in the recordNot stated
Red HatRed Hat OpenShift Container Platform 4Not specified in the recordNot stated
Red HatRed Hat Openshift Data Foundation 4Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. Scored by CNA (redhat.com).

Official description

A flaw was found in the multicloud-operators-subscription component. This vulnerability allows a user on a managed cluster to escalate their privileges by creating a Subscription with specific, crafted annotations. Successful exploitation grants the attacker the ability to deploy resources into any namespace with the elevated permissions of the controller's Service Account, potentially leading to unauthorized access and control over cluster resources.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How developers prevent this class of flaw

  • Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in Multicluster Global Hub 1.4.9

All Multicluster Global Hub 1.4.9 vulnerabilities

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.