Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-4740: Cross-cluster privilege escalation in Open Cluster Management certificate renewal validation

Published Apr 7, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.2High · v3.1
EPSS0.15%4th percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Red Hat
IdentifiersCVE-2026-4740CWE-295 · Improper Certificate Validation

CVE-2026-4740 is an improper certificate validation flaw in Open Cluster Management (OCM), which underlies Red Hat Advanced Cluster Management (ACM) and Red Hat Multi Cluster Engine. The issue affects the Kubernetes client certificate renewal flow used by managed-cluster agents to authenticate to the hub cluster. According to the provided content, the vulnerable CertificateSigningRequest approval logic on the hub validates certificate identity fields using a prefix-based comparison derived from a user-controlled label/server-name calculation rather than enforcing an exact match between the requesting managed cluster identity and the cluster name embedded in the certificate request. As a result, an administrator of one managed cluster can craft a forged CSR for another cluster whose name shares the relevant prefix, obtain approval from the OCM controller, and receive a valid client certificate for the target cluster identity. The forged credentials can then be used to interact with hub-side OCM resources such as ManifestWork and pivot into other managed clusters or the hub itself.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation enables cross-cluster privilege escalation from one managed cluster to other managed clusters and potentially to the hub cluster. An attacker who already has administrator access on a managed cluster can impersonate another cluster's agent identity, patch or abuse ManifestWork distribution, and deploy privileged resources such as a ClusterRoleBinding on the victim cluster. This can result in full administrative control of the victim managed cluster and may extend to compromise of the hub cluster, with high impact to confidentiality, integrity, and availability across the cluster fleet.

Mitigation

If you can’t patch tonight, do this now.

Until fixes are applied, reduce exposure by tightly restricting administrator access on managed clusters, since exploitation requires managed-cluster admin privileges. Audit and limit access to hub kubeconfig secrets stored in agent namespaces on managed clusters. Review cluster naming conventions to avoid predictable or overlapping prefix relationships that could facilitate impersonation, and closely monitor hub CSR approvals, ManifestWork modifications, and unexpected ClusterRoleBinding deployments. Where operationally feasible, constrain network paths and API access between managed clusters and the hub, and prioritize protection of hub clusters named with predictable defaults such as "local-cluster."

Remediation

Patch, then assume compromise.

Apply the vendor-provided fixes from Red Hat/Open Cluster Management for CVE-2026-4740 so that CSR approval enforces exact cluster identity validation during Kubernetes client certificate renewal. Because the issue affects OCM and downstream products that depend on it, update affected Open Cluster Management, Red Hat Advanced Cluster Management, and Red Hat Multi Cluster Engine deployments to the corrected releases referenced by the vendor advisory. After patching, rotate or reissue potentially exposed agent credentials and review previously approved CSRs and ManifestWork changes for signs of abuse.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Red HatAdvanced Cluster Management For Kubernetesapplication
FAQ

Frequently asked questions

Is CVE-2026-4740 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-4740 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-4740?
Yes. As of Sep 25, 2026, Mallory has reports of a public exploit for CVE-2026-4740.
Is there a patch for CVE-2026-4740?
Apply the vendor-provided fixes from Red Hat/Open Cluster Management for CVE-2026-4740 so that CSR approval enforces exact cluster identity validation during Kubernetes client certificate renewal. Because the issue affects OCM and downstream products that depend on it, update affected Open Cluster Management, Red Hat Advanced Cluster Management, and Red Hat Multi Cluster Engine deployments to the corrected releases referenced by the vendor advisory.
What products are affected by CVE-2026-4740?
Red Hat Advanced Cluster Management For Kubernetes.
How severe is CVE-2026-4740?
CVE-2026-4740 has a CVSS v3.1 score of 8.2 (High) and an EPSS score of 0.15% (4th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity5Community discussion across Reddit, Mastodon, and other social sources.