# CVE-2026-71576: Missing authorization in Multicluster Global Hub 1.4.9

> Attackers can falsify or delete critical cluster data by manipulating self-asserted source identities in CloudEvents due to improper validation.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 29 Sep 2026
- **Also known as:** GHSA-q5c4-r3vh-f379

## What is CVE-2026-71576?

CVE-2026-71576 is a high-severity missing authorization vulnerability in Red Hat Multicluster Global Hub 1.4.9, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in multicluster-global-hub. The manager component improperly validates the source identity of incoming CloudEvents on Kafka status topics. A remote attacker, after compromising a managed hub and obtaining its Kafka client certificate, can manipulate the self-asserted source identity. This allows the attacker to falsify or delete critical data, such as compliance, inventory, and cluster health information, belonging to other hubs in the database.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2026-71576?


## How do I fix CVE-2026-71576?

No fix has been published for CVE-2026-71576 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-71576 being exploited?

There is no known exploitation of CVE-2026-71576 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71576 and fix it if it is affected.

What it is: CVE-2026-71576 is a high-severity missing authorization vulnerability in Red Hat Multicluster Global Hub 1.4.9, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-71576 in the wild and no public exploit code.

Affected product: Red Hat Multicluster Global Hub 1.4.9. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-71576/ (Markdown: https://insights.sbomify.com/CVE-2026-71576/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71576
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71576
- OSV: https://osv.dev/vulnerability/CVE-2026-71576

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-71576/
Summaries are generated and may contain mistakes; the official description above is the record.