CVE
Red Hat Multicluster Engine for Kubernetes unauthorized cluster access in hypershift-addon
Affects Multicluster Engine for Kubernetes and Multicluster Engine for Kubernetes 5 environments that use the hypershift addon, where a low-privileged authenticated user can view, modify, or delete managed cluster resources.
- Exploited
- No known exploitation
- Fix
- See vendor advisory
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Multicluster engine environments that use the hypershift addon
Summary
The hypershift-addon operator in Red Hat Multicluster Engine for Kubernetes grants its permissions to all authenticated users instead of only the addon service. Remotely, a low-privileged logged-in user can view, modify, or delete managed cluster resources, which could disrupt clusters across the managed fleet.
Original description
A flaw was found in hypershift-addon. Due to an overly permissive role-based access control (RBAC) configuration that grants permissions to all authenticated users rather than restricting them to the addon service, a low-privileged authenticated user can view, modify, or delete managed cluster resources. This improper authorization allows unauthorized users to alter or disrupt clusters across the entire managed fleet.
Who should check
Teams running Red Hat Multicluster Engine for Kubernetes with the hypershift addon, and any hub users with valid credentials on those hubs
“In multicluster engine environments utilizing the hypershift addon”
cve.now Index
- Exploitation0/40No signal
- Exposure8/25Specific setups only, reachable over the network
- Reach10/20Shipped in major Linux distributions
- Severity8.1/10CVSS 8.1
- No patch5/5No fixed version listed; see vendor advisory
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 38 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Multicluster engine environments that use the hypershift addonWorkaround: The checked facts do not describe a workaround or a way to limit the hypershift addon. Until a fix is available, the sources offer no specific mitigation.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-132229 (Hypershift-addon: hypershift-addon: overly permissive clusterrolebinding allows any authenticated user to modify and delete managed clusters), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-132229 (entry last updated 2026-11-18):
Affected:
- Red Hat Multicluster Engine for Kubernetes: version range not reported
- Red Hat Multicluster Engine for Kubernetes 5: version range not reported
Fixed versions: none listed yet.
Conditions (all must be true for the bug to be hit):
- Multicluster engine environments that use the hypershift addon (source: https://access.redhat.com/security/cve/cve-2026-132229)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-132229 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-132229 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://access.redhat.com/security/cve/CVE-2026-132229
- https://access.redhat.com/security/cve/cve-2026-132229
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-132229
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-132229"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- multicluster-engine/hypershift-addon-rhel9-operator
Version range not reported
- multicluster-engine/hypershift-addon-rhel9-operator
Version range not reported
Evidence 3
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-132229 |
| Record | NVD · CVE-2026-132229 |
| Other links 1 | |
| Link | access.redhat.com · security/cve/CVE-2026-132229 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-132229
Is CVE-2026-132229 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An overly permissive clusterrolebinding in the hypershift-addon lets any authenticated user, including low-privileged ones, view, modify, or delete managed cluster resources. This can alter or disrupt clusters across the managed fleet.Source: access.redhat.com
Am I affected, and how do I check?
The affected products are Multicluster Engine for Kubernetes and Multicluster Engine for Kubernetes 5, in environments that use the hypershift addon. The checked facts do not list specific affected version ranges, so check whether the hypershift addon is in use in a multicluster engine environment and which product version is installed.Source: access.redhat.com
How do I fix CVE-2026-132229?
The checked facts name no fixed version and no patch identifiers, so no upgrade target can be given from these sources. Follow the vendor's advisory for the current fix status.Source: access.redhat.com
What if there's no patch?
The checked facts do not describe a workaround or a way to limit the hypershift addon. Until a fix is available, the sources offer no specific mitigation.Source: access.redhat.com