RHSA-2026:82811HighCVSS 8.3

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

Published
October 22, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (10)

CVE-2026-58014 →CVE-2026-68121 →CVE-2026-80844 →CVE-2026-81000 →CVE-2026-11822 →CVE-2026-11824 →CVE-2026-54369 →CVE-2026-58015 →CVE-2026-74469 →CVE-2026-5260 →

📋 Description

CVE-2026-5260 — gnutls: gnutls: Information disclosure via heap overread in RSA key exchange 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-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-58015 — glib: path traversal in glib/gio/gdbusauthmechanismsha1.c via keyring_lookup_entry and mechanism_client_data_receive CVE-2026-68121 — kernel: pppoe: reload header pointer after dev_hard_header() CVE-2026-74469 — kernel: sctp: prevent peer transport count overflow CVE-2026-80844 — kernel: xfrm: ah6: validate routing header segments_left CVE-2026-81000 — kernel: net: tun: bound receive headroom

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.15 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.15/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:75d3e0923552cf9db351f8301695cb2a0fecd9f71140885bd9c4d63cccb83aff (For s390x architecture) The image digest is sha256:cebb116deac8cbab25722ef996784a7e988a87d39bfca0a260d39dcb750af14f (For ppc64le architecture) The image digest is sha256:317636d528facd317a09b04f4a5437b039e7fb6870f51d891341507200483f01 (For aarch64 architecture) The image digest is sha256:59c7df31559e4f7ccccfef1d52cd2a2b28afb7b411401e68c0e240d4c9c9ef0b All OpenShift Container Platform 4.15 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.15/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: 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 vulnerability, ensure that applications only connect to trusted D-Bus servers and operate within secure, isolated networks to prevent man-in-the-middle (MitM) attacks. If feasible, configuring the D-Bus connection to strictly require the EXTERNAL authentication mechanism and disabling DBUS_COOKIE_SHA1 will completely neutralize this issue. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (13)