Red Hat Security Advisory: OpenShift Container Platform 4.12.82 bug fix and security update
🔗 CVE IDs covered (6)
📋 Description
CVE-2025-5994 — unbound: Unbound Cache poisoning CVE-2025-6965 — sqlite: Integer Truncation in SQLite CVE-2025-9566 — podman: Podman kube play command may overwrite host files CVE-2025-49794 — libxml: Heap use after free (UAF) leads to Denial of service (DoS) CVE-2025-49796 — libxml: Type confusion leads to Denial of service (DoS) CVE-2025-58060 — cups: Authentication Bypass in CUPS Authorization Handling
🎯 Affected products2
- Red Hat OpenShift Container Platform 4.12
- rhcos-x86_64-412.86.202510291903-0 as a component of Red Hat OpenShift Container Platform 4.12
✅ Remediation
For OpenShift Container Platform 4.12 see the following documentation, which will be updated shortly for this release, for important instructions on how to upgrade your cluster and fully apply this asynchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64, s390x, ppc64le, and aarch64 architectures. The image digests may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:d26fd3fd30ac6ae13f2779045d4e2defbf77aa24db5393d91df19488fd42504d All OpenShift Container Platform 4.12 users are advised to upgrade to these updated packages and images when they are available in the appropriate release channel. To check for available updates, use the OpenShift CLI (oc) or web console. Instructions for upgrading a cluster are available at https://docs.redhat.com/en/documentation/openshift_container_platform/4.12/html-single/updating_clusters/index#updating-cluster-within-minor. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Red Hat advises to not run the podman kube play command with untrusted Kubernetes YAML file as input, additionally review the Kubernetes YAML file before running it through podman may help to catch maliciously crafted secretes or volumes that may be used to exploit this vulnerability. Workaround: There's no available mitigation other than avoid processing untrusted XML documents before updating to the libxml version containing the fix. Workaround: There's no available mitigation other than to avoid processing untrusted XML documents if the user is unable/unwilling to update the library. Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to a widespread installation base, or stability. It is strongly advised to apply vendor-supplied patches as soon as they are released to address this authentication bypass vulnerability.
🔗 References (9)
- selfhttps://access.redhat.com/errata/RHSA-2025:19894
- externalhttps://access.redhat.com/security/updates/classification/#important
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2372373
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2372385
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2380149
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2380949
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2392595
- externalhttps://bugzilla.redhat.com/show_bug.cgi?id=2393152
- selfhttps://security.access.redhat.com/data/csaf/v2/advisories/2025/rhsa-2025_19894.json