RHSA-2026:95508CriticalCVSS 9.8

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

Published
November 9, 2026
Last Modified
November 12, 2026

🔗 CVE IDs covered (15)

CVE-2026-42013 →CVE-2026-80792 →CVE-2026-111497 →CVE-2026-98432 →CVE-2025-47273 →CVE-2026-16313 →CVE-2026-28390 →CVE-2026-59999 →CVE-2026-42011 →CVE-2026-45445 →CVE-2026-89846 →CVE-2026-34182 →CVE-2026-45447 →CVE-2026-59995 →CVE-2026-60002 →

📋 Description

CVE-2025-47273 — setuptools: Path Traversal Vulnerability in setuptools PackageIndex CVE-2026-16313 — sg3_utils: sg3_utils: arbitrary command execution via udev property injection in sg_inq --export CVE-2026-28390 — openssl: OpenSSL: Denial of Service due to NULL pointer dereference in CMS EnvelopedData processing CVE-2026-34182 — openssl: CMS AuthEnvelopedData Processing May Accept Forged Messages CVE-2026-42011 — gnutls: gnutls: Security bypass due to incorrect name constraint handling CVE-2026-42013 — gnutls: gnutls: Certificate validation bypass due to oversized Subject Alternative Name CVE-2026-45445 — openssl: AES-OCB IV Ignored on EVP_Cipher() Path CVE-2026-45447 — openssl: Heap Use-After-Free in OpenSSL PKCS7_verify() 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-80792 — kernel: ipv6: fix use-after-free in ip6_finish_output2() CVE-2026-89846 — kernel: scsi: qla2xxx: Bound rsp_info_len to avoid OOB sense-data read CVE-2026-98432 — kernel: ipv4: free inet_opt and ireq_opt after an RCU grace period CVE-2026-111497 — brotli: Out-of-Bounds Write in Google Brotli Decoder

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.14 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.14/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:3141b63f379bfbc8f19ea61ae23532199efe2cc90740fb22ff5b67c808557968 (For s390x architecture) The image digest is sha256:6ead21766e93bd4365be9b11e0d7d3b61706da78075fd20307568dfe1790318c (For ppc64le architecture) The image digest is sha256:33fd2434da5abcfae6de499092569fb159c9a29efbf8ddc9f5e87a67a5e8880a (For aarch64 architecture) The image digest is sha256:f0a1a76229b14f928ad7c5600f26062c32dd8d01806f893c5ba492a9b3c45cc8 All OpenShift Container Platform 4.14 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.14/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: 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: Applications that process Cryptographic Message Syntax (CMS) EnvelopedData messages should be configured to only accept input from trusted sources. Restricting network access to services that process untrusted CMS data can also reduce exposure to this Denial of Service vulnerability. 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: If QLogic Fibre Channel HBAs are not in use, the 'qla2xxx' kernel module can be blacklisted to prevent it from loading. This can be achieved by creating a modprobe configuration file. To blacklist the module: 1. Create a file named `/etc/modprobe.d/blacklist-qla2xxx.conf` with the following content: `blacklist qla2xxx` 2. Regenerate the initramfs to ensure the blacklist is applied during boot: `sudo dracut -f -v` (for RHEL 7/8/9) `sudo mkinitcpio -P` (for Arch-based systems, if applicable) 3. Reboot the system for the changes to take effect. Warning: Blacklisting this module will disable functionality for QLogic Fibre Channel HBAs. Ensure that this hardware is not required before applying this mitigation. A system reboot is required for the changes to take effect. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (18)