Skip to main content
CVE-2024-45337VulnerabilityPublished Updated

Red Hat Security Advisory: Multicluster Engine for Kubernetes 2.7.3 security updates and bug fixes

Affects Red HatSource GCVE Database

0
Compare

Mentioned vulnerabilities

Not known to be exploited.

Data as of 29 Oct 2026, 09:13 UTC

Severity
High

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
3.1% chance of exploitation in 30 days – higher than 88% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Jan 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Red Hat Product Security Red HatAffected
  • Red Hat
  • multicluster engine for Kubernetes
  • multicluster engine for Kubernetes 2.7 for RHEL 9
  • multicluster engine for Kubernetes 2.7 for RHEL 8
  • s390x
Fixed in–

Description

Multicluster engine for Kubernetes v2.7.3 images Multicluster engine for Kubernetes provides the foundational components that are necessary for the centralized management of multiple Kubernetes-based clusters across data centers, public clouds, and private clouds. You can use the engine to create new Red Hat OpenShift Container Platform clusters or to bring existing Kubernetes-based clusters under management by importing them. After the clusters are managed, you can use the APIs that are provided by the engine to distribute configuration based on placement policy. Security fix(es): * nanoid mishandles non-integer values (CVE-2024-55565) * Misuse of ServerConfig.PublicKeyCallback may cause authorization bypass in golang.org/x/crypto (CVE-2024-45337)

References

Community reviews

Loading reviews…