RHSA-2026:66357HighCVSS 8.1

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

Published
September 15, 2026
Last Modified
October 1, 2026

🔗 CVE IDs covered (11)

CVE-2026-13204 →CVE-2026-15816 →CVE-2026-58015 →CVE-2026-72693 →CVE-2026-9547 →CVE-2026-43133 →CVE-2026-55973 →CVE-2026-58014 →CVE-2026-8286 →CVE-2026-11721 →CVE-2026-11824 →

📋 Description

CVE-2026-8286 — curl: curl: Insecure connection establishment due to TLS configuration mismatch CVE-2026-9547 — curl: curl: Man-in-the-middle attack via SSH host key bypass CVE-2026-11721 — bind: bind9: Cache poisoning via label count discrepancy, RRSIG, wildcards CVE-2026-11824 — sqlite: SQLite: Arbitrary code execution and crash via heap-based buffer overflow in FTS5 CVE-2026-13204 — bind: bind9: Unexpected exit with NSEC and NSEC3 both present CVE-2026-15816 — dracut: dracut: root code execution via unescaped error message written to sourced emergency hook script in die() CVE-2026-43133 — kernel: KVM: nSVM: Always use vmcb01 in VMLOAD/VMSAVE emulation CVE-2026-55973 — unbound: Unbound: Denial of Service via malformed EDNS Report-Channel option 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-72693 — kbd: Local privilege escalation in openvt via incorrect process owner verification allowing passwordless root login

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.22 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.22/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:e74e45ada5ab6325586e559ea69b7fd23bfe620af960bef33af19cadea8db7d2 (For s390x architecture) The image digest is sha256:347eda8880ab4c686d434f7c4283643e2dc24beb105921b056fbdb8bdd0846ac (For ppc64le architecture) The image digest is sha256:307f108a7f85343b693cb29ddc34cf96e7d059c118b460af0e988e0b3f80c407 (For aarch64 architecture) The image digest is sha256:f15ec71d866b8cc0ee85d082f185822b418d002e76bea7bc2ae1cbff6e0abf56 All OpenShift Container Platform 4.22 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.22/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: Restrict DHCP server access on networks used for network boot (DHCP snooping, dedicated/trusted provisioning VLANs) until a fix is available. 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 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: To mitigate this issue, avoid using `openvt -u` in privileged `kbrequest`/init deployments. Instead, configure the keyboard request to initiate a standard authenticated login on the new virtual terminal, or disable the keyboard request binding entirely until a fix is available. Changes to `kbrequest` configurations may require a system restart or service reload to take effect.

🔗 References (14)