RHSA-2026:95229CriticalCVSS 9.8

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

Published
November 9, 2026
Last Modified
November 14, 2026

🔗 CVE IDs covered (10)

CVE-2026-45445 →CVE-2026-60002 →CVE-2026-34182 →CVE-2026-59995 →CVE-2026-59999 →CVE-2026-86145 →CVE-2026-89161 →CVE-2026-98432 →CVE-2026-103111 →CVE-2026-111497 →

📋 Description

CVE-2026-34182 — openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages CVE-2026-45445 — openssl: AES-OCB IV Ignored on EVP_Cipher() Path 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-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-98432 — kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period CVE-2026-103111 — pcre2: pcre2: Out-of-bounds write via crafted regular expression CVE-2026-111497 — brotli: Out-of-Bounds Write in Google Brotli Decoder

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.16 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.16/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:4eda35319bd4f1cf62676d74e2ca48c772e55114f81c373fc09d01f75f83b4ce (For s390x architecture) The image digest is sha256:e12d7cf01e5550b04ab451fc70a0e327ac4ed894a7c1d0ed6220b73c0c06bfff (For ppc64le architecture) The image digest is sha256:3de3edc1eeea830893554c5af1092821dbeb767ec6a3e23eefffb478d6515a39 (For aarch64 architecture) The image digest is sha256:3968ebf80043423de593d2655e9e1382a6f5e54acd97bd0b214ce88d8837cc2b All OpenShift Container Platform 4.16 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.16/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: 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 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. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (13)