CVE-2026-4740
Redhat Advanced Cluster Management For Kubernetes privilege escalation
- Published7 Apr 2026
Description
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/errata/RHSA-2026:11414
- https://access.redhat.com/errata/RHSA-2026:13542
- https://access.redhat.com/errata/RHSA-2026:13853
- https://access.redhat.com/errata/RHSA-2026:8218
- https://access.redhat.com/errata/RHSA-2026:9848
- https://access.redhat.com/security/cve/CVE-2026-4740
- https://blog.arfevrier.fr/open-cluster-management-cross-cluster-escape/
- https://bugzilla.redhat.com/show_bug.cgi?id=2450590
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-4740.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-4740 being actively exploited?
CVE-2026-4740 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.16%.
How severe is CVE-2026-4740?
CVE-2026-4740 has a CVSS 3.1 base score of 8.2, rated high. EPSS estimates a 0.16% probability of exploitation.
Which products are affected by CVE-2026-4740?
Affected products include Redhat Advanced Cluster Management For Kubernetes.
How do I fix CVE-2026-4740?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-4740 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.