RHSA-2026:89725CriticalCVSS 9.1

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

Published
October 27, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (18)

CVE-2026-80864 →CVE-2026-43114 →CVE-2026-68121 →CVE-2026-80863 →CVE-2026-89161 →CVE-2026-99999 →CVE-2026-34182 →CVE-2026-45445 →CVE-2026-80792 →CVE-2026-86145 →CVE-2026-114406 →CVE-2026-54369 →CVE-2026-103111 →CVE-2026-58014 →CVE-2026-59995 →CVE-2026-59999 →CVE-2026-60002 →CVE-2026-64564 →

📋 Description

CVE-2026-34182 — openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages CVE-2026-43114 — kernel: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry CVE-2026-45445 — openssl: AES-OCB IV Ignored on EVP_Cipher() Path 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" CVE-2026-59995 — openssh: OpenSSH: sftp client allows attacker to control downloaded file location CVE-2026-59999 — openssh: OpenSSH sshd: Security bypass due to incorrect handling of forwarding and tunneling options CVE-2026-60002 — openssh: OpenSSH: Use-after-free vulnerability during host key re-exchange on the client side CVE-2026-64564 — kernel: sctp: don't free the ASCONF's own transport in DEL-IP processing CVE-2026-68121 — kernel: pppoe: reload header pointer after dev_hard_header() CVE-2026-80792 — kernel: ipv6: fix use-after-free in ip6_finish_output2() CVE-2026-80863 — kernel: RDMA/rxe: Fix OOB in free_rd_atomic_resources() CVE-2026-80864 — kernel: RDMA/rxe: Fix responder UAF on IB_QP_MAX_DEST_RD_ATOMIC modify_qp CVE-2026-86145 — pcre2: PCRE2: Out-of-bounds write allows arbitrary code execution via crafted regular expressions CVE-2026-89161 — pcre2: PCRE2: Memory corruption vulnerability in pcre2_jit_match CVE-2026-99999 — kernel: ipv4: validate checksum_start before completing checksum CVE-2026-103111 — pcre2: pcre2: Out-of-bounds write via crafted regular expression CVE-2026-114406 — ca-certificates: Distrust eMudhra intermediate CA certificates due to security concerns

🎯 Affected products5

  • Red Hat OpenShift Container Platform 4.18
  • rhcos-aarch64-418.94.202610242013-0 as a component of Red Hat OpenShift Container Platform 4.18
  • rhcos-ppc64le-418.94.202610242013-0 as a component of Red Hat OpenShift Container Platform 4.18
  • rhcos-s390x-418.94.202610242013-0 as a component of Red Hat OpenShift Container Platform 4.18
  • rhcos-x86_64-418.94.202610242013-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:dabe7545163af58a2538c645725556acea531fdcfb83fd5aea9b7f28cd112c06 (For s390x architecture) The image digest is sha256:37753fc25221075037cbca9e1c6f0e14f08f33cc86b668efbd5c1fb5453d7fc9 (For ppc64le architecture) The image digest is sha256:7f5637b4be7768839c338e81312e9deb5c5b6f20a694e72f0746d4245d9e90fb (For aarch64 architecture) The image digest is sha256:22447d72c8c01d104946efa2e951a0c3fff37eb753d5c6ee7cf3ff3615c738d3 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: Systems configured to operate in FIPS mode are not affected by this vulnerability. To mitigate this issue, ensure that OpenSSL is operating in FIPS mode by enabling the system-wide FIPS policy. This may have broader implications for cryptographic operations on the system and should be evaluated for compatibility with existing applications. A system reboot may be required for the changes to take effect. 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: 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. Workaround: To mitigate this issue, avoid using the `sftp server:/path .` command when connecting to untrusted or potentially malicious SFTP servers. Exercise caution and verify the authenticity of SFTP servers before initiating file transfers, especially when using commands that implicitly define the download destination, and also avoid running SFTP sessions with elevated privileges (such as root). Workaround: To mitigate this issue, if `DisableForwarding=yes` is set in `/etc/ssh/sshd_config` to prevent all forwarding, ensure that `PermitTunnel` is explicitly set to `no` in the same configuration file. This will enforce the intended security policy. After modifying `/etc/ssh/sshd_config`, restart the `sshd` service for the changes to take effect. This may temporarily interrupt active SSH sessions. Workaround: To mitigate this issue, OpenSSH clients should only connect to trusted SSH servers. Enforcing strict host key checking and carefully managing `known_hosts` files can help prevent connections to servers with unexpected or altered host keys, thereby reducing exposure to this client-side vulnerability. Workaround: To mitigate this issue, prevent the `sctp` kernel module from loading. Create a file named `/etc/modprobe.d/disable-sctp.conf` with the following content: ``` install sctp /bin/true blacklist sctp ``` After creating the file, regenerate the initramfs and reboot the system for the changes to take effect. Applications or services that rely on the SCTP protocol cannot use this mitigation and should prioritize applying the fix. Workaround: See the security bulletin for a detailed mitigation procedure. Workaround: To mitigate this issue, prevent module rdma_rxe from being loaded. Please see https://access.redhat.com/solutions/41278 for how to blacklist a kernel module to prevent it from loading automatically. Workaround: To mitigate this issue, prevent the rdma_rxe kernel module from being loaded. 1. Create a configuration file in /etc/modprobe.d to disable loading of the module: # echo "install rdma_rxe /bin/true" > /etc/modprobe.d/disable-rdma_rxe.conf 2. If the module is currently loaded, attempt to unload it: # modprobe -r rdma_rxe Caveats: Disabling this module prevents the creation and operation of software RDMA over Converged Ethernet (Soft-RoCE) devices. Applications requiring rdma_rxe will fail to initialize. If the module is currently in active use and cannot be unloaded dynamically, a system reboot is required to ensure the module is fully disabled. Workaround: To mitigate this Improper Protection of Alternate Path vulnerability, ensure that secondary execution branches—such as the reuse of cached memory workspaces—enforce the exact same size and boundary checks as the primary memory allocation paths. Limit exposure by preventing untrusted user input from directly controlling PCRE2 regular expressions, and strictly avoid utilizing recursive matching patterns when operating under a low heap limit. Apply a defense-in-depth strategy by validating all inputs comprehensively.

🔗 References (21)