Advisory record · GHSA-q4gv-pjmh-c735

Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation

CVSS 8.2 HighEPSS 0.0015 · 4th percentile

Published by the GitHub Advisory Database at 7 Apr 2026, 15:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
open-cluster-management.io/ocmGo<1.2.11.2.1
Identifiers
GHSA-q4gv-pjmh-c735 · CVE-2026-4740 · GO-2026-5564
Weakness (CWE)
CWE-295
Published
7 Apr 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Open Cluster Management (ocm), the module open-cluster-management.io/ocm, is vulnerable in versions before 1.2.1. An administrator of a managed cluster can forge a client certificate that the OCM controller approves, which allows privilege escalation across clusters, potentially including the hub cluster. Upgrade to version 1.2.1 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.2 High 3.1 CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H CNA (redhat)
  • CISA KEV Not listed.
  • EPSS 0.0015, the 4th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:06 UTC First seen by agentprime
  2. 31 Oct 2026, 15:06 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.