CVE-2026-71576
Auth validation flaw in multicluster-global-hub allows cross-hub data tampering.
Is CVE-2026-71576 being exploited?
Not confirmed. CVE-2026-71576 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.12% probability of exploitation in the next 30 days.
How severe is CVE-2026-71576?
CVE-2026-71576 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-71576?
Not known from our data. No patch reference has been recorded for CVE-2026-71576, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-71576 affect?
CVE-2026-71576 affects multicluster-global-hub (manager), Kafka status topics, Managed hub Kafka clients/certificates. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-71576?
Isolate compromised hubs, rotate Kafka client certs, restrict cert issuance, apply vendor patch when available.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
If a managed hub's Kafka client cert is compromised, attacker can impersonate other hubs to falsify or delete compliance, inventory, and cluster health data.
Immediate action required