RHSA-2026:34048HighCVSS 7.8

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

Published
July 9, 2026
Last Modified
August 6, 2026

🔗 CVE IDs covered (3)

CVE-2026-1519 →CVE-2026-46243 →CVE-2026-46331 →

📋 Description

CVE-2026-1519 — bind: BIND: Denial of Service via maliciously crafted DNSSEC-validated zone CVE-2026-46243 — kernel: Linux kernel: smb: client: reject userspace cifs.spnego descriptions CVE-2026-46331 — kernel: net/sched: act_pedit: extend the writable skb range per key

🎯 Affected products2

  • Red Hat OpenShift Container Platform 4.12
  • rhcos-x86_64-412.86.202606251120-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:746f1a33a0b89a5489916b10366777b2672b65cfcd0cdfaffe5a710e3aa15f35 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: To mitigate this issue, disable DNSSEC validation on affected BIND resolvers. Alternatively, configure the BIND server as authoritative-only if recursive queries are not required. Disabling DNSSEC validation may reduce the security posture of the DNS resolver. A restart of the BIND service (`named`) is required for these changes to take effect and may temporarily interrupt DNS resolution. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (6)