RHSA-2026:65907HighCVSS 8.0

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

Published
September 17, 2026
Last Modified
October 1, 2026

🔗 CVE IDs covered (5)

CVE-2026-2340 →CVE-2026-3012 →CVE-2026-11822 →CVE-2026-11824 →CVE-2026-16313 →

📋 Description

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-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-16313 — sg3_utils: sg3_utils: arbitrary command execution via udev property injection in sg_inq --export

🎯 Affected products2

  • Red Hat OpenShift Container Platform 4.12
  • rhcos-x86_64-412.86.202609082051-0 as a component of Red Hat OpenShift Container Platform 4.12

✅ Remediation

For OpenShift Container Platform 4.12 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.12/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:0ba3b9ea13531f643027339fef1e1a1e04bd4d87f3387f25e6d7e3dfa64bad52 All OpenShift Container Platform 4.12 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.12/html-single/updating_clusters/index#updating-cluster-within-minor. 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: Remove or comment out the REMOVE_CMD rule from 50-udev-default.rules to prevent command execution on device removal. Alternatively, if automatic SCSI device identification is not required, disable the udev rule that invokes sg_inq --export on device connection.

🔗 References (8)