CyberSecBulletin
CVE-2026-75569NVD status: Awaiting Analysis

multicluster engine for Kubernetes 2.10: Reliance on Insufficiently Trustworthy Component

Published Updated By the CyberSecBulletin desk

CVE-2026-75569 is a high-severity reliance on insufficiently trustworthy component vulnerability in multicluster engine for Kubernetes 2.10 from Red Hat, with a CVSS 3.1 base score of 7.7 out of 10. It can be exploited remotely over the network by an attacker with administrator privileges, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 0.6% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of multicluster engine for Kubernetes 2.10 you run against the affected versions below, and install the vendor's latest release.

Affected products and versions

VendorProductAffected versionsFixed in
Red Hatmulticluster engine for Kubernetes 2.10Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.11Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.17Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.6Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.8Not specified in the recordNot stated
Red Hatmulticluster engine for Kubernetes 2.9Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (redhat.com).

Official description

A flaw was found in mce-operator-bundle. The build process fetches and executes scripts from a remote repository without performing integrity checks, such as commit pinning or signature verification. This allows a malicious actor with write access to the remote repository to inject and execute arbitrary code during the build. The consequence is a compromised build process, potentially leading to the distribution of malicious software.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Reliance on Insufficiently Trustworthy Component

The product is built from multiple separate components, but it uses a component that is not sufficiently trusted to meet expectations for security, reliability, updateability, and maintainability.

How developers prevent this class of flaw

  • Regardless of the source, each component should be sufficiently trusted to ensure correct, secure operation of the product. For each component, ensure that its supply chain is well-controlled with sub-tier suppliers using best practices. For third-party software components such as libraries, ensure that they are developed and actively maintained by reputable vendors.
  • Maintain a Bill of Materials for all components and sub-components of the product. For software, maintain a Software Bill of Materials (SBOM). According to, An SBOM is a formal, machine-readable inventory of software components and dependencies, information about those components, and their hierarchical relationships.
  • Continue to monitor changes in each of the product's components, especially when the changes indicate new vulnerabilities, end-of-life (EOL) plans, supplier practices that affect trustworthiness, etc.

More Reliance on Insufficiently Trustworthy Component vulnerabilities (CWE-1357)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in multicluster engine for Kubernetes 2.10

All multicluster engine for Kubernetes 2.10 vulnerabilities

Recent Reliance on Insufficiently Trustworthy Component vulnerabilities

Spotted an error? Tell us.