VulnerabilityPublished 10 Aug 2026Updated 29 Sep 2026

CVE-2026-71577: multicluster-global-hub · CWE-522

Affects multicluster-global-hubSource GCVE Database

Compare

Authoritative record:CVE-2026-71577· Medium 6.3

Not known to be exploited · CVSS 6.3 Medium : upgrade to 1.7.3 or 1.4.9 when convenient.

Data as of 13 Nov 2026, 23:54 UTC

CVSS 3.1 base score

6.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.7.3, 1.4.9

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

Attack Vector: Network
Attack Complexity: High
Privileges Required: Low
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 10 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-v7q5-q7p3-9vjm

What to do

Upgrade multicluster-global-hub to 1.7.3 or 1.4.9.

Patches and advisories

Affected software

Product	Affected	Fixed in
GitHubmulticluster-global-hub`pkg:github/multicluster-global-hub`Other threats	Affected <1.4.9 <1.7.3	Fixed in 1.4.9 1.7.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Red Hat has released official security updates for Multicluster Global Hub versions 1.4.9 and 1.7.3 that address this vulnerability. Users should apply these updates promptly to remediate the issue. The vendor advisory does not indicate any temporary workarounds or that no action is required. Patch status is confirmed by Red Hat advisories RHSA-2026:67516 and RHSA-2026:67842. No cloud service remediation applies as this is not a cloud-hosted service.

Description

A vulnerability in multicluster-global-hub allows a compromised managed hub to gain read access to a shared communication topic during ManagedClusterMigration. This flaw enables interception of sensitive bootstrap kubeconfigs containing API server tokens intended for other hubs. These tokens have an extended validity of about 9.86 years, increasing the risk of unauthorized access and information disclosure across managed clusters. The issue has a CVSS score of 6.3 (medium severity). Red Hat has released security updates addressing this vulnerability in versions 1.4.9 and 1.7.3 of Multicluster Global Hub.

Impact

The vulnerability allows an attacker who has compromised one managed hub to read sensitive bootstrap kubeconfigs intended for other hubs. These kubeconfigs contain API server tokens with extended validity (~9.86 years), which could be used to gain unauthorized access to other managed clusters. This leads to a significant confidentiality breach risk across the multicluster environment. There is no indication of integrity or availability impact. No known exploits in the wild have been reported.

CWE-522Insufficiently Protected Credentials (opens in a new tab)
Class weaknessOWASP Top 10 A06:2025: Insecure Design (opens in a new tab)
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
Architecture and Design
Use an appropriate security mechanism to protect the credentials.
Architecture and Design
Make appropriate use of cryptography to protect the credentials.
Implementation
Use industry standards to protect the credentials (e.g. LDAP, keystore, etc.).
OWASP Cheat Sheets
Secure Design Principles (opens in a new tab)
OWASP ASVS 4.0.3
V2.10.3 (opens in a new tab)
V2.8.5 (opens in a new tab)
V2.8.4 (opens in a new tab)
Attack patterns
Session Sidejacking (opens in a new tab)
Signature Spoofing by Key Theft (opens in a new tab)
Password Recovery Exploitation (opens in a new tab)
Kerberoasting (opens in a new tab)
Modify Existing Service (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Patches and advisories

Affected software

Description

AI analysisMachine-generated, updated 29 Sep 2026, 21:21 UTC

WeaknessesCWE-522

Technical details

References

Community reviews

Related threats