Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-19130 medium CVSS 5.8

Vulnerability in multicluster-engine (CVE-2026-19130)

Summary

Vulnerability in multicluster-engine (CVE-2026-19130). Confidential information can be exposed externally. Exploitable via copiedFrom.

Original description

The description as published by the source.

A flaw was found in the provider-credential-controller component of multicluster-engine (MCE). An attacker with specific permissions on the hub cluster, and knowledge of a prior credential value, could exploit an authorization bypass vulnerability. By manipulating copiedFrom labels, the attacker could intercept newly rotated provider credentials, leading to unauthorized information disclosure. This allows access to sensitive credentials that should otherwise be protected.

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-19130 has been found in multicluster-engine.
Attackers can target a specific entry point like copiedFrom over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 5.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "multicluster-engine CVE-2026-19130" on the vendor's site.

CVE-2026-19130 (multicluster-engine) — CWE-639 / CVSS v3 5.8
Attack vector: remote (network-reachable)
Attack surface: copiedFrom
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-639) exists in multicluster-engine. Attackers reach the vulnerable code path via copiedFrom.

📍 Affected scope

Check the vendor advisory for the affected versions of multicluster-engine. Attack surface: copiedFrom.

🔥 Severity

Severity: Medium (CVSS 5.8/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 request patterns matching this CVE's known IOCs. Run grep -r 'multicluster-engine' . 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 'multicluster-engine' . | grep -v node_modules

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

  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