Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-7163 medium CVSS 6.1

Vulnerability in Multicluster Engine (CVE-2026-7163)

Summary

Vulnerability in Multicluster Engine (CVE-2026-7163). Confidential information can be exposed externally. Exploitable via GET /v2/clusters/{cluster_id}/credentials.

Original description

The description as published by the source.

A vulnerability in the assisted-service REST API, an optional Assisted Installer (assisted-service) component in the Multicluster Engine (MCE), allows an authenticated user with minimal namespace-scoped privileges to obtain administrative credentials for arbitrary clusters provisioned through the hub.

The credentials download endpoint (GET /v2/clusters/{cluster_id}/credentials, which returns the kubeadmin password) and the kubeconfig download endpoint are operational in AUTH_TYPE=local mode, the only authentication mode available in on-premises ACM/MCE hub deployments. The local authenticator unconditionally grants full administrative access to any request bearing a valid JWT, with no per-endpoint restrictions. A valid local JWT is embedded as a plaintext query parameter in InfraEnvStatus.ISODownloadURL and is readable by any user who has get rights on an InfraEnv object in their own namespace.

The affected components ship as part of Multicluster Engine (MCE). The Red Hat Advanced Cluster Management (ACM) deployments that include MCE are equally affected.
This issue does not affect the hosted SaaS offering (console.redhat.com), which uses a different authentication mode.

Successful exploitation gives the attacker the kubeadmin password and kubeconfig for any OpenShift cluster provisioned through the affected hub, granting unrestricted root-level administrative access to those spoke clusters.

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-7163 has been found in Multicluster Engine.
Attackers can target a specific entry point like GET /v2/clusters/{cluster_id}/credentials over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Multicluster Engine CVE-2026-7163" on the vendor's site.

CVE-2026-7163 (Multicluster Engine) — CWE-312 / CVSS v3 6.1
Attack vector: adjacent-network
Attack surface: GET /v2/clusters/{cluster_id}/credentials
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-312) exists in Multicluster Engine. Attackers reach the vulnerable code path via GET /v2/clusters/{cluster_id}/credentials.

📍 Affected scope

Check the vendor advisory for the affected versions of Multicluster Engine. Attack surface: GET /v2/clusters/{cluster_id}/credentials.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Confidential information can be exposed externally.

🔧 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 GET /v2/clusters/{cluster_id}/credentials requests with malformed payloads or SQL meta-characters. 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
    Hunt for indicators of compromise detect 
    grep 'GET /v2/clusters/{cluster_id}/credentials' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで GET /v2/clusters/{cluster_id}/credentials への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Post-deployment verification verify 
    Replay attack against GET /v2/clusters/{cluster_id}/credentials on staging to confirm patch closes the vector

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

References

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