RHSA-2026:20040HighCVSS 8.2

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

Published
May 27, 2026
Last Modified
October 30, 2026

🔗 CVE IDs covered (6)

CVE-2026-27135 →CVE-2026-35385 →CVE-2026-35535 →CVE-2026-3497 →CVE-2026-4424 →CVE-2026-5121 →

📋 Description

CVE-2026-3497 — openssh: OpenSSH GSSAPI: Information disclosure or denial of service due to uninitialized variables CVE-2026-4424 — libarchive: libarchive: Information disclosure via heap out-of-bounds read in RAR archive processing CVE-2026-5121 — libarchive: libarchive: Arbitrary code execution via integer overflow in ISO9660 image processing CVE-2026-27135 — nghttp2: nghttp2: Denial of Service via malformed HTTP/2 frames after session termination CVE-2026-35385 — OpenSSH: OpenSSH: Privilege escalation via scp legacy protocol when not preserving file mode CVE-2026-35535 — sudo: Sudo: Privilege escalation due to failure in privilege drop calls

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.19 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.19/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:1bd5ad0745f446a798a4038e4d04cf651213f71bc4e76dd9349f5c6968135f9b (For s390x architecture) The image digest is sha256:e1cd4053fdab99ef5530074cb61596de6d0c3b0fd091763051e93b69b4a47c11 (For ppc64le architecture) The image digest is sha256:5fbe6fe21a35a4541ce893b558425dc362678b74521a8cc3ead986f4e7a8021c (For aarch64 architecture) The image digest is sha256:34e28f68135a822d581cb955afb867f600d83e9ed8dd4284847df24e90802d6d All OpenShift Container Platform 4.19 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.19/html-single/updating_clusters/index#updating-cluster-cli. Workaround: To mitigate this issue, disable GSSAPI key exchange in the OpenSSH server configuration. This prevents the server from processing GSSAPI messages, eliminating the vulnerability's attack surface. Edit `/etc/ssh/sshd_config` and add or modify the line: ``` GSSAPIKeyExchange no ``` After saving the changes, restart the `sshd` service for the mitigation to take effect. This action will prevent users from authenticating via GSSAPI. ``` # systemctl restart sshd ``` 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 processing untrusted ISO9660 images with applications that utilize `libarchive`. Users should only extract or read content from ISO images obtained from trusted sources. 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. Users of affected Red Hat products should install the updated sudo packages available through their product's standard update channels.

🔗 References (9)