RHSA-2026:89838CriticalCVSS 8.8

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

Published
October 27, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (7)

CVE-2026-114406 →CVE-2026-43114 →CVE-2026-64564 →CVE-2026-86145 →CVE-2026-89161 →CVE-2026-99999 →CVE-2026-103111 →

📋 Description

CVE-2026-43114 — kernel: netfilter: nft_set_pipapo_avx2: don't return non-matching entry on expiry CVE-2026-64564 — kernel: sctp: don't free the ASCONF's own transport in DEL-IP processing 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.14
  • rhcos-aarch64-414.92.202610242240-0 as a component of Red Hat OpenShift Container Platform 4.14
  • rhcos-ppc64le-414.92.202610242240-0 as a component of Red Hat OpenShift Container Platform 4.14
  • rhcos-s390x-414.92.202610242240-0 as a component of Red Hat OpenShift Container Platform 4.14
  • rhcos-x86_64-414.92.202610242240-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:37f1faf5a14324a24756dd53c07e91e51616110aa5535b0c54471a43a8cf14fa (For s390x architecture) The image digest is sha256:fbe773c859fae7da27a998508d4f875d9add8eb42224870c62a291d7104853aa (For ppc64le architecture) The image digest is sha256:70f9848df813a062885bbc6c5a24c6916c7b9da8560515c230763e82c72a089f (For aarch64 architecture) The image digest is sha256:0cc9177f9eba20e2136a9e06389810d89d298c387424b9398164e5fa4af4aec3 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: 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: 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 (10)