RHSA-2026:70586HighCVSS 8.6

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

Published
October 1, 2026
Last Modified
October 5, 2026

🔗 CVE IDs covered (16)

CVE-2026-11822 →CVE-2026-58014 →CVE-2025-66418 →CVE-2026-2340 →CVE-2026-11824 →CVE-2026-10723 →CVE-2026-11331 →CVE-2026-14164 →CVE-2026-6893 →CVE-2026-13321 →CVE-2026-15816 →CVE-2026-16313 →CVE-2026-54369 →CVE-2026-3012 →CVE-2026-3039 →CVE-2026-5946 →

📋 Description

CVE-2025-66418 — urllib3: urllib3: Unbounded decompression chain leads to resource exhaustion CVE-2026-2340 — samba: vfs_worm does not block directory modification CVE-2026-3012 — samba: group policy certificate enrollment uses http:// without validation 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-10723 — bind: bind9: Incorrect acceptance of NSEC3 records CVE-2026-11331 — bind9: bind: Potential wildcard CNAME RPZ policy bypass CVE-2026-11822 — sqlite: SQLite: Arbitrary code execution via crafted FTS5 full-text search data CVE-2026-11824 — sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 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() CVE-2026-16313 — sg3_utils: sg3_utils: arbitrary command execution via udev property injection in sg_inq --export CVE-2026-54369 — acl: Symlink traversal privilege escalation via libacl functions CVE-2026-58014 — glib: off-by-one error in glib/gkeyfile.c via "g_key_file_get_locale_string_list"

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.17 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.17/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:027c19a0057cf115fdf33dd8a018a9f5195842afcd3a540e8dcd68ec398cbbce (For s390x architecture) The image digest is sha256:f1599fb9c86085b366ddceda999779fb694c0c9442251742c1385e994c4268af (For ppc64le architecture) The image digest is sha256:36544f009e7f95a1d7bc77dc47937abee8c7c4cae1634503b02d5b697b869815 (For aarch64 architecture) The image digest is sha256:79597f64234864ba104ffd99bb4773fed1f6f0797c06f84583a0604119649046 All OpenShift Container Platform 4.17 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.17/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: Administrators can mitigate this issue by: Setting read-only permissions on protected files at the underlying filesystem level will prevent modifications. Configuring ```worm:grace_period = 0``` (zero or less) in smb.conf will eliminate the writable grace period (will eliminate the window in which the rename can happen), understanding that this may impact workflows requiring multi-step file creation. Workaround: Systems are not affected unless Samba Group Policy processing and certificate auto-enrollment are explicitly enabled. Administrators can reduce exposure by: Avoiding unnecessary use of certificate auto-enrollment. Ensuring your "smb.conf" does not contain a line like ```apply group policies = yes```. If , group policy is not be enabled, the vulnerable code will not run. Intercepting the HTTP request requires some control over the local network or other devices to intercept or redirect traffic. Some network administrators might assess this as a low risk on their networks. 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. Workaround: Remove or comment out the REMOVE_CMD rule from 50-udev-default.rules to prevent command execution on device removal. Alternatively, if automatic SCSI device identification is not required, disable the udev rule that invokes sg_inq --export on device connection. Workaround: Restrict unprivileged users from creating symlinks in directories that privileged processes operate on with ACL commands. Where possible, use the fs.protected_symlinks sysctl (enabled by default on RHEL 7+), which prevents symlink following in world-writable sticky directories unless the owner of the symlink matches the owner of the target file or directory. Workaround: To mitigate this vulnerability, implement input validation to sanitize untrusted key files (such as .desktop or .ini files), specifically rejecting or stripping empty values before calling g_key_file_get_locale_string_list(). Alternatively, restricting the application to only load key files from trusted sources will completely neutralize this issue.

🔗 References (21)