RHSA-2026:65839HighCVSS 9.0

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

Published
September 17, 2026
Last Modified
September 17, 2026

🔗 CVE IDs covered (20)

CVE-2026-3833 →CVE-2026-11824 →CVE-2026-15816 →CVE-2026-33846 →CVE-2026-43112 →CVE-2026-6893 →CVE-2026-14164 →CVE-2026-29111 →CVE-2026-1933 →CVE-2026-3012 →CVE-2026-4408 →CVE-2026-41411 →CVE-2026-42010 →CVE-2025-5222 →CVE-2026-2340 →CVE-2026-11822 →CVE-2026-33845 →CVE-2026-34982 →CVE-2026-42009 →CVE-2026-48864 →

📋 Description

CVE-2025-5222 — icu: Stack buffer overflow in the SRBRoot::addTag function CVE-2026-1933 — samba: Missing access check on reparse point operations CVE-2026-2340 — samba: vfs_worm does not block directory modification CVE-2026-3012 — samba: group policy certificate enrollment uses http:// without validation CVE-2026-3833 — gnutls: GnuTLS: Policy bypass due to case-sensitive nameConstraints comparison CVE-2026-4408 — samba: Remote Code Execution in SAMR CVE-2026-6893 — dracut: dracut: Root code execution via DHCP options command injection 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-14164 — libarchive: Double-Free Vulnerability in RAR5 Decompression Logic via dangling filtered_buf pointer in init_unpack() CVE-2026-15816 — dracut: dracut: root code execution via unescaped error message written to sourced emergency hook script in die() CVE-2026-29111 — systemd: systemd: Arbitrary code execution or Denial of Service via spurious IPC API call data CVE-2026-33845 — gnutls: GnuTLS: Denial of Service via DTLS zero-length fragment CVE-2026-33846 — gnutls: GnuTLS: Denial of Service via heap buffer overflow in DTLS handshake fragment reassembly CVE-2026-34982 — vim: arbitrary command execution via modeline sandbox bypass CVE-2026-41411 — vim: Vim: Command injection allows arbitrary code execution via malicious tag files CVE-2026-42009 — gnutls: gnutls: Denial of Service via DTLS packet reordering vulnerability CVE-2026-42010 — gnutls: gnutls: Authentication Bypass via NUL Character in Username CVE-2026-43112 — kernel: fs/smb/client: fix out-of-bounds read in cifs_sanitize_prepath CVE-2026-48864 — libsolv: Heap buffer overflow in libsolv repopagestore via unchecked decompression of malicious .solv page data

🎯 Affected products2

  • Red Hat OpenShift Container Platform 4.13
  • rhcos-x86_64-413.92.202609080414-0 as a component of Red Hat OpenShift Container Platform 4.13

✅ Remediation

For OpenShift Container Platform 4.13 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.13/html/release_notes You may download the oc tool and use it to inspect release image metadata for x86_64 architecture. The image digest may be found at https://quay.io/repository/openshift-release-dev/ocp-release?tab=tags. The sha value for the release is as follows: (For x86_64 architecture) The image digest is sha256:57d3bc54220249ddc77cbcea17171e0240fe2c6d8be3ce83865bea30950862cd All OpenShift Container Platform 4.13 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.13/html-single/updating_clusters/index#updating-cluster-within-minor. 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: Administrators can mitigate this issue by ensuring users who access a read only = yes Samba share do not have filesystem-level write permission to the exported files. A server administrator may also monitor and remove unintended "user.SmbReparse" xattr (extended attributes) and the associated FILE_ATTRIBUTE_REPARSE_POINT "user.DosAttrib" bit metadata if exploitation is suspected. Workaround: Administrators can mitigate this issue by: Setting read-only permissions on protected files at the underlying filesystem level will prevent modifications. Configuring ```worm:grace_period = 0``` (zero or less) in smb.conf will eliminate the writable grace period (will eliminate the window in which the rename can happen), understanding that this may impact workflows requiring multi-step file creation. Workaround: Systems are not affected unless Samba Group Policy processing and certificate auto-enrollment are explicitly enabled. Administrators can reduce exposure by: Avoiding unnecessary use of certificate auto-enrollment. Ensuring your "smb.conf" does not contain a line like ```apply group policies = yes```. If , group policy is not be enabled, the vulnerable code will not run. Intercepting the HTTP request requires some control over the local network or other devices to intercept or redirect traffic. Some network administrators might assess this as a low risk on their networks. 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, ensure that systems configured to obtain network settings via DHCP in the initramfs are only booted on trusted networks. This vulnerability requires an attacker to control a DHCP server on the adjacent network segment. If network configuration via DHCP is not strictly necessary during the initramfs phase, consider using static network configuration. Workaround: No mitigation is currently available that meets Red Hat Product Security's standards for usability, deployment, applicability, or stability. Customers are advised to apply the appropriate security update once it becomes available. Workaround: Restrict DHCP server access on networks used for network boot (DHCP snooping, dedicated/trusted provisioning VLANs) until a fix is available. Workaround: To mitigate this issue, disable the modeline support by adding the following command to the Vim configuration file: ~~~ set nomodeline ~~~ Workaround: Mitigation for this issue involves exercising caution when opening or processing tag files from untrusted sources. Users should avoid loading tag files from unknown or suspicious origins to prevent the execution of arbitrary commands. Workaround: To mitigate this issue, prevent the `cifs` kernel module from loading if CIFS client functionality is not required. This can be achieved by blacklisting the module. Create a file named `/etc/modprobe.d/blacklist-cifs.conf` with the following content: ``` blacklist cifs ``` After creating the file, regenerate the initramfs and reboot the system for the changes to take effect. ```bash dracut -f -v reboot ``` Disabling the `cifs` module will prevent the system from mounting CIFS network shares, which may impact functionality relying on this protocol.

🔗 References (23)