CVE-2026-66801

Public on

Last Modified: UTC

Critical Critical severity What does this mean?
9.9 CVSS v3 Score Breakdown

Description

A flaw was found in multicluster-global-hub. An attacker who compromises a managed hub can leverage its legitimate Kafka client certificate to publish a CloudEvent (a specification for describing event data in a common way) message to the shared gh-spec topic. This message can spoof its source as "global-hub" and target other managed hubs. Due to a lack of binding between the Kafka client principal and the CloudEvent envelope, the agent on the targeted hub accepts this spoofed message and applies arbitrary resources. This vulnerability allows for fleet-wide cluster-admin privilege escalation across all managed hubs.

Statement

Critical: The default Strimzi transport in Multicluster Global Hub is vulnerable to privilege escalation. A compromised managed hub can exploit weak Kafka Write ACLs on the shared gh-spec topic and spoofed CloudEvent sources to gain cluster-admin privileges across the entire fleet of managed hubs. This allows an attacker to achieve fleet-wide administrative control from a single compromised leaf hub.

Mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

Additional information

External References

Affected Packages and Issued Red Hat Security Errata

Unless explicitly stated as not affected, all previous versions of packages in any minor update stream of a product listed here should be assumed vulnerable, although may not have been subject to full analysis.

Products / Services Components State Errata
Multicluster Global Hub 1.4.5 multicluster-globalhub/multicluster-globalhub-rhel9-operator Fixed RHSA-2026:55810
Multicluster Global Hub 1.6.5 multicluster-globalhub/multicluster-globalhub-rhel9-operator Fixed RHSA-2026:54392
Multicluster Global Hub 1.7.0 multicluster-globalhub/multicluster-globalhub-rhel9-operator Fixed RHSA-2026:53530
Multicluster Global Hub 1.8.0 multicluster-globalhub/multicluster-globalhub-rhel9-operator Fixed RHSA-2026:52946
Red Hat multicluster global hub 1.5.1 multicluster-globalhub/multicluster-globalhub-rhel9-operator Fixed RHSA-2026:54577

Common Vulnerability Scoring System (CVSS) Score Details

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 Authorities (CNA) source for its products and services (see Red Hat classifications ).

CVSS v3 Score Breakdown

Red Hat NVD cve.org
CVSS v3 Base Score 9.9 N/A N/A
Attack Vector Network N/A N/A
Attack Complexity Low N/A N/A
Privileges Required Low N/A N/A
User Interaction None N/A N/A
Scope Changed N/A N/A
Confidentiality Impact High N/A N/A
Integrity Impact High N/A N/A
Availability Impact High N/A N/A

CVSS v3 Vector

Red Hat CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Red Hat CVSS v3 Score Explanation

9.9 Critical. PR:L — attacker needs authenticated access to any one managed hub (namespace-admin or compromised agent pod). S:C — compromised hub-A's Kafka principal is scoped to hub-A, but the attack crosses into hub-B and all other managed hubs fleet-wide. AC:L — no race conditions or special configuration needed; the shared Write ACL on gh-spec and the absent principal-to-source binding are default-on in Strimzi transport mode.

Frequently Asked Questions

Why is Red Hat's CVSS v3 score or Impact different from other vendors?

 For open source software shipped by multiple vendors, the CVSS base scores may vary for each vendor's version depending on the version they ship, how they ship it, the platform, and even how the software is compiled. This makes scoring of vulnerabilities difficult for third-party vulnerability databases such as NVD that only provide a single CVSS base score for each vulnerability. Red Hat scores reflect how a vulnerability affects our products specifically.

For more information, see https://access.redhat.com/solutions/762393.

My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
  • "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
  • "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.

What can I do if my product is listed as "Will not fix"?

 A "will not fix" status means that a fix for an affected product version is not planned or not possible due to complexity, which may create additional risk.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.

What can I do if my product is listed as "Fix deferred"?

 A deferred status means that a fix for an affected product version is not guaranteed due to higher-priority development work.

Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
  • Apply a mitigation (if one exists).
  • Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
  • Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.

What is a mitigation?

 A mitigation is an action that can be taken to reduce the impact of a security vulnerability, without deploying any fixes.

I have a Red Hat product but it is not in the above list, is it affected?

 The listed products were found to include one or more of the components that this vulnerability affects. These products underwent a thorough evaluation to determine their affectedness by this vulnerability. Note that layered products (such as container-based offerings) that consume affected components from any of the products listed in this table may be affected and are not represented.

Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?

 In order to maintain code stability and compatibility, Red Hat usually does not rebase packages to entirely new versions. Instead, we backport fixes and new features to an older version of the package we distribute. This can result in some security scanners that only consider the package version to report the package as vulnerable. To avoid this, we suggest that you use an approved vulnerability scanner from our This content is not included.Red Hat Vulnerability Scanner Certification program.

My product is listed as "Out of Support Scope". What does this mean?

 When a product is listed as "Out of Support Scope", it means a vulnerability with the impact level assigned to this CVE is no longer covered by its current support lifecycle phase. The product has been identified to contain the impacted component, but analysis to determine whether it is affected or not by this vulnerability was not performed. The product should be assumed to be affected. Customers are advised to apply any mitigation options documented on this page, consider removing or disabling the impacted component, or upgrade to a supported version of the product that has an update available.