Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-73267 high CVSS 7.7

Vulnerability in multicluster engine (CVE-2026-73267)

Summary

Vulnerability in multicluster engine (CVE-2026-73267). Risk of unauthorized operations or information disclosure. Exploitable via spec.namespace.

Original description

The description as published by the source.

A flaw was found in the clusterclaims-controller component of multicluster engine (MCE). A tenant with standard permissions to create and delete ClusterClaim resources can exploit this by manipulating the spec.namespace field. This allows the tenant to specify and delete any ManagedCluster, including the hub's local-cluster or other tenants' clusters, due to a missing ownership check. This vulnerability can lead to a denial of service by enabling unauthorized deletion of ManagedClusters.

Source: GitHub Security Advisories (Global) 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-73267 has been found in multicluster engine.
Attackers can target a specific entry point like spec.namespace over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 7.7/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "multicluster engine CVE-2026-73267" on the vendor's site.

CVE-2026-73267 (multicluster engine) — CWE-602 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: spec.namespace
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-602) exists in multicluster engine. Attackers reach the vulnerable code path via spec.namespace.

📍 Affected scope

Check the vendor advisory for the affected versions of multicluster engine. Attack surface: spec.namespace.

🔥 Severity

Severity: High (CVSS 7.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ 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. Audit SBOM/dependencies to find affected services.

Response actions

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

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで multicluster engine を使っているサービスとバージョンを洗い出す。

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

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

References

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