Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-4740 high CVSS 8.2

Vulnerability in open-cluster-management.io/ocm (CVE-2026-4740)

Summary

Vulnerability in open-cluster-management.io/ocm (CVE-2026-4740). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 1.2.1 or later.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-4740 has been found in open-cluster-management.io/ocm.
Successful exploitation can lead to full system takeover. CVSS score: 8.2/10.
What to do: upgrade open-cluster-management.io/ocm to 1.2.1 or later.
If unsure, ask your IT team or search "open-cluster-management.io/ocm CVE-2026-4740" on the vendor's site.

CVE-2026-4740 (open-cluster-management.io/ocm) — CWE-295 / CVSS v3 8.2
Attack vector: local / no user interaction
Patched: 1.2.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-295) exists in open-cluster-management.io/ocm.

📍 Affected scope

Check the vendor advisory for the affected versions of open-cluster-management.io/ocm.

🔥 Severity

Severity: High (CVSS 8.2/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.2.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'open-cluster-management.io/ocm' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'open-cluster-management.io/ocm' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で open-cluster-management.io/ocm を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade open-cluster-management.io/ocm to 1.2.1

    ステージング環境で 1.2.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go open-cluster-management.io/ocm
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.2.1"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details