Red Hat Bug Fix Advisory: Multicluster Engine for Kubernetes 2.5.5 bug fix updates
Affects Red HatSource GCVE Database
Not known to be exploited : upgrade to 2.5.5 when convenient.
Data as of 25 Oct 2026, 19:02 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.5
Exploitation evidence
Disclosed: evidence found.
CVE published 10 Jul 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.
What to do
Upgrade Red Hat to 2.5.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Product Security Red Hat | Affected
| Fixed in
|
AI-suggested
Red Hat has released version 2.5.5 of the Multicluster Engine for Kubernetes to fix this issue. Users should upgrade affected versions (>=2.5.0 and <2.5.5) to 2.5.5 or later to resolve the cluster status problem. Refer to Red Hat's official documentation for installation and upgrade instructions. No additional mitigation actions are indicated by the vendor.
Description
Red Hat issued a bug fix advisory for Multicluster Engine for Kubernetes version 2.5.5 that addresses an issue where local and HCP clusters show an unknown status after an ACM update. This issue is tracked as CVE-2024-4068 and affects versions from 2.5.0 up to but not including 2.5.5. The Multicluster Engine enables centralized management of multiple Kubernetes clusters across different environments. The update resolves the cluster status problem reported in Jira issue ACM-12584.