Quick answers
- Is CVE-2026-71576 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-71576 being exploited in the wild.
- How severe is CVE-2026-71576?
- High severity, with a CVSS score of 8.5, published 10 August 2026.
- Which products and versions are affected?
- Red Hat Multicluster Global Hub before 1.4.9.
- Is there a fix for CVE-2026-71576?
- A patch was published on 2026-09-15: Fixed in Multicluster Global Hub 1.4.9 (RHSA-2026:67516) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-71576 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-71576?
- Check whether you run Red Hat Multicluster Global Hub at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is an authentication bypass in the manager component's validation of CloudEvents received from Kafka status topics. The root cause is improper verification of source identity claims in incoming messages, which are self-asserted rather than cryptographically verified. An attacker who has compromised a managed hub and obtained its Kafka client certificate can manipulate the source identity field to impersonate other hubs, sending malicious CloudEvents to the manager. This allows arbitrary modification or deletion of compliance, inventory, and cluster health data in the database. The attack requires prior compromise of a managed hub to obtain valid Kafka credentials, limiting the immediate attack surface. Patches are available in Multicluster Global Hub 1.4.9 and later.
Affected products
- Red Hat Multicluster Global Hub before 1.4.9
Timeline
- 2026-08-10: disclosed
- 2026-09-15: patched: Fixed in Multicluster Global Hub 1.4.9 (RHSA-2026:67516)