Red Hat Security Advisory: multicluster Engine for Kubernetes 2.5.9 container updates
Affects Red HatSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited : upgrade to 2.5.9 soon.
Data as of 25 Oct 2026, 22:09 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.5.9
Exploitation evidence
Disclosed: evidence found.
CVE published 5 May 2025
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.9.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Red Hat Product Security Red Hat | Affected
| Fixed in
|
AI-suggested
Red Hat has released updated container images in multicluster Engine for Kubernetes version 2.5.9 that fix these vulnerabilities. Users should upgrade to version 2.5.9 or later to remediate the issues. Refer to Red Hat's official documentation for installation instructions. No additional mitigations are specified in the advisory.
Description
multicluster engine for Kubernetes v2.5.9 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): * golang.org/x/oauth2/jws: Unexpected memory consumption during token parsing in golang.org/x/oauth2/jws (CVE-2025-22868) * golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing (JWT) (CVE-2025-30204)
References
- access.redhat.com/errata/RHSA-2025:4473 (opens in a new tab)
- access.redhat.com/security/updates/classification/ (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2348366 (opens in a new tab)
- bugzilla.redhat.com/show_bug.cgi?id=2354195 (opens in a new tab)
- security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_4473.json (opens in a new tab)