CVE-2026-4740: Rhacm: open cluster management (ocm): cross-cluster privilege escalation via improper kubernetes client certificate renewal validation
A flaw was found in Open Cluster Management (OCM), the technology underlying Red Hat Advanced Cluster Management (ACM). Improper validation of Kubernetes client certificate renewal allows a managed cluster administrator to forge a client certificate that can be approved by the OCM controller. This enables cross-cluster privilege escalation and may allow an attacker to gain control over other managed clusters, including the hub cluster.
Security readout for executives and security teams
Plain-English summary
This issue could let an administrator on one managed cluster abuse Open Cluster Management certificate renewal handling to gain privileges across other managed clusters, possibly including the hub. That turns a contained cluster-admin compromise into a broader platform-control risk.
Executive priority
Treat this as high priority where ACM or MCE manages multiple production clusters. The business risk is privilege expansion from one cluster into the broader fleet, including potential hub impact. Prioritize inventory, vendor guidance, and access review.
Technical view
OCM, underlying Red Hat ACM, improperly validates Kubernetes client certificate renewals. A managed cluster administrator may forge a client certificate that the OCM controller approves, enabling cross-cluster privilege escalation. The source maps this to CWE-295 and CVSS 8.2 with changed scope and high confidentiality, integrity, and availability impact.
Likely exposure
Organizations using Red Hat Advanced Cluster Management or Multicluster Engine for Kubernetes with OCM-managed clusters are the likely exposure group. The bundle names multiple multicluster-engine packages, but does not provide affected version ranges.
Exploitation context
The CVSS vector indicates local access, low complexity, high privileges, and no user interaction. The attacker already needs managed cluster administrator privileges. KEV is false, and the supplied sources do not state active exploitation in the wild.
Researcher notes
Public evidence supports the vulnerability class, impact, affected product family, and severity. Affected version ranges, fixed package versions, and exploitation telemetry are incomplete in the supplied bundle, so validation should lean on Red Hat’s CVE, Bugzilla, and CSAF VEX records.
Mitigation direction
Review Red Hat CVE and CSAF VEX guidance for affected and fixed builds.
Apply Red Hat-provided updates when available for multicluster-engine components.
Limit managed cluster administrator access to trusted operators only.
Monitor certificate renewal and approval workflows for unexpected identities.
Review hub and managed cluster trust boundaries after any cluster-admin compromise.
Validation and detection
Inventory Red Hat ACM and Multicluster Engine deployments using OCM.
Compare installed multicluster-engine packages against Red Hat CSAF VEX status.
Review who has administrator rights on each managed cluster.
Audit certificate approval logs for unusual renewal patterns or identities.
Check for unexpected cross-cluster administrative actions after certificate renewals.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
7Timeline events
2ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-295 · source CWE mapping
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.