RHSA-2026:62549HighCVSS 9.1

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

Published
September 10, 2026
Last Modified
September 11, 2026

🔗 CVE IDs covered (21)

CVE-2025-49796 →CVE-2025-54518 →CVE-2026-1519 →CVE-2026-3012 →CVE-2026-3833 →CVE-2026-13321 →CVE-2025-9566 →CVE-2025-49794 →CVE-2026-2340 →CVE-2026-5946 →CVE-2026-6893 →CVE-2026-11331 →CVE-2026-39821 →CVE-2025-6965 →CVE-2026-3039 →CVE-2026-10723 →CVE-2026-15816 →CVE-2026-29111 →CVE-2026-43112 →CVE-2025-5994 →CVE-2025-9230 →

📋 Description

CVE-2025-5994 — unbound: Unbound Cache poisoning CVE-2025-6965 — sqlite: Integer Truncation in SQLite CVE-2025-9230 — openssl: Out-of-bounds read & write in RFC 3211 KEK Unwrap CVE-2025-9566 — podman: Podman kube play command may overwrite host files CVE-2025-49794 — libxml: Heap use after free (UAF) leads to Denial of service (DoS) CVE-2025-49796 — libxml: Type confusion leads to Denial of service (DoS) CVE-2025-54518 — kernel: xen: AMD Zen 2 Processors: Privilege escalation via improper CPU cache isolation CVE-2026-1519 — bind: BIND: Denial of Service via maliciously crafted DNSSEC-validated zone 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-3039 — bind: BIND 9 server memory exhaustion during GSS-API TKEY negotiation CVE-2026-3833 — gnutls: GnuTLS: Policy bypass due to case-sensitive nameConstraints comparison CVE-2026-5946 — bind: BIND: Denial of Service via specially crafted DNS messages CVE-2026-6893 — dracut: dracut: Root code execution via DHCP options command injection CVE-2026-10723 — bind: bind9: Incorrect acceptance of NSEC3 records CVE-2026-11331 — bind9: bind: Potential wildcard CNAME RPZ policy bypass CVE-2026-13321 — bind: bind9: DNSSEC Validation Bypass via Out-of-Zone NSEC Next Field 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-39821 — golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing CVE-2026-43112 — kernel: fs/smb/client: fix out-of-bounds read in cifs_sanitize_prepath

🎯 Affected products5

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

✅ Remediation

For OpenShift Container Platform 4.16 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.16/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:077bb2d0f053cfadc673374237b206740ab78f2663d3dbd1b49713c2ced88994 (For s390x architecture) The image digest is sha256:a46bf8cdae866571521a66b6efa1634db5109b020ab9ed6d8de1caf815bfe25a (For ppc64le architecture) The image digest is sha256:6e0b33f7d8db91651807aabffce25e1cdf27f90a6240ac49bd651c64b05464c3 (For aarch64 architecture) The image digest is sha256:e76b87d63f7b8b2960353d5cc3e7bf427b65edd8e95c8c51fbb7c12a6ea4fb34 All OpenShift Container Platform 4.16 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.16/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: Red Hat advises to not run the podman kube play command with untrusted Kubernetes YAML file as input, additionally review the Kubernetes YAML file before running it through podman may help to catch maliciously crafted secretes or volumes that may be used to exploit this vulnerability. Workaround: There's no available mitigation other than avoid processing untrusted XML documents before updating to the libxml version containing the fix. Workaround: There's no available mitigation other than to avoid processing untrusted XML documents if the user is unable/unwilling to update the library. 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: 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. Example: ```bash # Edit /etc/named.conf and remove or comment out lines related to tkey-gssapi-keytab or tkey-gssapi-credential. # For example, remove or comment out: # key "gssapi-key" { # algorithm GSSAPI; # secret "BASE64_ENCODED_KEY"; # }; # # Then reload the named service: systemctl reload named ``` Reloading the `named` service may cause a brief interruption in DNS resolution. 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: Disclaimer: The following mitigation notes are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. ISC states no workarounds exist. Until patched, restrict the resolver to authorized client networks and deploy separate resolvers per trust zone. Memory hardening and auth controls don't apply — this is a DNS protocol logic error using validly-signed records. Workaround: Restrict DHCP server access on networks used for network boot (DHCP snooping, dedicated/trusted provisioning VLANs) until a fix is available. Workaround: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds.

🔗 References (24)