RHSA-2025:8542: Important: Red Hat Advanced Cluster Management 2.13.3 fixes and container updates
Important: Red Hat Advanced Cluster Management 2.13.3 fixes and container updates
Other sources
Red Hat Advanced Cluster Management for Kubernetes 2.13.3 images<br>Red Hat Advanced Cluster Management for Kubernetes provides the<br>capabilities to address common challenges that administrators and site<br>reliability engineers face as they work across a range of public and<br>private cloud environments. Clusters and applications are all visible and<br>managed from a single console—with security policy built in.<br>This advisory contains the container images for Red Hat Advanced Cluster<br>Management for Kubernetes, which fix several bugs. See the following<br>Release Notes documentation, which will be updated shortly for this<br>release, for additional details about this release:<br><a href="https://docs.redhat.com/documentation/en-us/redhatadvancedclustermanagementforkubernetes/2.13/html/releasenotes/" target="blank">https://docs.redhat.com/documentation/en-us/redhatadvancedclustermanagementforkubernetes/2.13/html/releasenotes/</a> Security fixes:<br><li> golang-jwt/jwt: jwt-go allows excessive memory allocation during header parsing (CVE-2025-30204)</li>
— Red Hat
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2025:8542?
The severity of RHSA-2025:8542 is classified as important.
What vulnerability does RHSA-2025:8542 address?
RHSA-2025:8542 addresses vulnerabilities in Red Hat Advanced Cluster Management for Kubernetes 2.13.3.
How do I fix RHSA-2025:8542?
To fix RHSA-2025:8542, update Red Hat Advanced Cluster Management for Kubernetes to version 2.13.3 or later.
Which versions of Red Hat Advanced Cluster Management are affected by RHSA-2025:8542?
RHSA-2025:8542 affects versions prior to 2.13.3 of Red Hat Advanced Cluster Management for Kubernetes.
Is a reboot required after applying RHSA-2025:8542?
A reboot may not be necessary after applying RHSA-2025:8542, but it's best to follow your organization's patch management guidelines.