RHSA-2026:70615HighCVSS 8.6

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

Published
October 1, 2026
Last Modified
October 5, 2026

🔗 CVE IDs covered (8)

CVE-2026-14164 →CVE-2026-15816 →CVE-2025-66418 →CVE-2026-3039 →CVE-2026-5946 →CVE-2026-6893 →CVE-2026-11331 →CVE-2026-13321 →

📋 Description

CVE-2025-66418 — urllib3: urllib3: Unbounded decompression chain leads to resource exhaustion CVE-2026-3039 — bind: BIND 9 server memory exhaustion during GSS-API TKEY negotiation CVE-2026-5946 — bind: BIND: Denial of Service via specially crafted DNS messages CVE-2026-6893 — dracut: dracut: Root code execution via DHCP options command injection CVE-2026-11331 — bind9: bind: Potential wildcard CNAME RPZ policy bypass CVE-2026-13321 — bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field CVE-2026-14164 — libarchive: Double-Free Vulnerability in RAR5 Decompression Logic via dangling filtered_buf pointer in init_unpack() CVE-2026-15816 — dracut: dracut: root code execution via unescaped error message written to sourced emergency hook script in die()

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.18 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.18/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:630c143e63c6024267bf6f66cfc7c84366eb8a9dc022eaf7b411b8e1474ca183 (For s390x architecture) The image digest is sha256:c8c83e4f0f69910e8c6b49781e588daf810d5d39dbfa00d4ab3303b6b3ea8344 (For ppc64le architecture) The image digest is sha256:d2c057433a1cfa2470110843b7820d42ffa5f29043eb245a7bc07e7b06b5b561 (For aarch64 architecture) The image digest is sha256:b35c9facdf6f1920dc6feb4d9b7a4699608ee6ae70dba55f7fc9a45218b16f8d All OpenShift Container Platform 4.18 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.18/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. 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. Example: ```bash # Edit /etc/named.conf and remove or comment out lines related to tkey-gssapi-keytab or tkey-gssapi-credential. # For example, remove or comment out: # key "gssapi-key" { # algorithm GSSAPI; # secret "BASE64_ENCODED_KEY"; # }; # # Then reload the named service: systemctl reload named ``` Reloading the `named` service may cause a brief interruption in DNS resolution. 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: To mitigate this issue, ensure that systems configured to obtain network settings via DHCP in the initramfs are only booted on trusted networks. This vulnerability requires an attacker to control a DHCP server on the adjacent network segment. If network configuration via DHCP is not strictly necessary during the initramfs phase, consider using static network configuration. Workaround: Disclaimer: The following mitigation notes are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. ISC states no workarounds exist. Until patched, restrict the resolver to authorized client networks and deploy separate resolvers per trust zone. Memory hardening and auth controls don't apply — this is a DNS protocol logic error using validly-signed records. Workaround: No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the appropriate security update once it becomes available. Workaround: Restrict DHCP server access on networks used for network boot (DHCP snooping, dedicated/trusted provisioning VLANs) until a fix is available.

🔗 References (11)