RHSA-2026:0674HighCVSS 8.6

Red Hat Security Advisory: OpenShift Container Platform 4.19.22 bug fix and security update

Published
January 22, 2026
Last Modified
September 1, 2026

🔗 CVE IDs covered (5)

CVE-2025-40780 →CVE-2025-59375 →CVE-2025-8677 →CVE-2025-9230 →CVE-2025-40778 →

📋 Description

CVE-2025-8677 — bind: Resource exhaustion via malformed DNSKEY handling CVE-2025-9230 — openssl: Out-of-bounds read & write in RFC 3211 KEK Unwrap CVE-2025-40778 — bind: Cache poisoning attacks with unsolicited RRs CVE-2025-40780 — bind: Cache poisoning due to weak PRNG CVE-2025-59375 — firefox: thunderbird: expat: libexpat in Expat allows attackers to trigger large dynamic memory allocations via a small document that is submitted for parsing

🎯 Affected products5

  • Red Hat OpenShift Container Platform 4.19
  • rhcos-aarch64-4.19.9.6.202601130152-0 as a component of Red Hat OpenShift Container Platform 4.19
  • rhcos-ppc64le-4.19.9.6.202601130152-0 as a component of Red Hat OpenShift Container Platform 4.19
  • rhcos-s390x-4.19.9.6.202601130152-0 as a component of Red Hat OpenShift Container Platform 4.19
  • rhcos-x86_64-4.19.9.6.202601130152-0 as a component of Red Hat OpenShift Container Platform 4.19

✅ Remediation

For OpenShift Container Platform 4.19 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 synchronous errata update: https://docs.redhat.com/en/documentation/openshift_container_platform/4.19/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 values for the release are as follows: (For x86_64 architecture) The image digest is sha256:e4377ba202c97eccba15c3a428cd4e532a02d5420d5b8918cdd3284404abb1ba (For s390x architecture) The image digest is sha256:0a15e17381e77d0afdf331ae3c455e091ffd454cf69966f041abf28ad7494be9 (For ppc64le architecture) The image digest is sha256:b7ec15e179936b7c832c59ee3e68c70151d16e5cb9270d1bd0f7fb6dd78e438c (For aarch64 architecture) The image digest is sha256:87fd3d95d4b0f67500c624b64a1bf69873a8ef361612fed314066f01b78677ec All OpenShift Container Platform 4.19 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.19/html-single/updating_clusters/index#updating-cluster-cli. 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. To reduce risk, restrict recursive queries to trusted or internal networks only, and apply rate limiting or firewall rules to prevent excessive or repetitive requests. Enabling DNSSEC validation helps reject forged records, while isolating recursive resolvers from authoritative servers limits the impact of potential cache poisoning. Active monitoring of CPU usage, query volume, and cache anomalies can provide early warning of abuse or attacks. 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: While it is not possible to eliminate risk from this vulnerability, there are several options for reducing the risk. These include restricting recursive queries to trusted or internal networks only, and apply rate limiting or firewall rules to prevent excessive or repetitive requests. Enabling DNSSEC validation helps reject forged records, while isolating recursive resolvers from authoritative servers limits the impact of potential cache poisoning. Active monitoring of CPU usage, query volume, and cache anomalies can provide early warning of abuse or attacks. Workaround: To mitigate the issue, limit XML input size and complexity before parsing, and avoid accepting compressed or deeply nested XML. Use OS-level resource controls (like ulimit or setrlimit()) to cap memory usage, or run the parser in a sandboxed or isolated process with strict memory and CPU limits. This helps prevent denial-of-service by containing excessive resource consumption.

🔗 References (8)