RHSA-2026:68534HighCVSS 8.2

Red Hat Security Advisory: OpenShift Container Platform 4.19.48 packages and security update

Published
September 23, 2026
Last Modified
October 5, 2026

🔗 CVE IDs covered (10)

CVE-2026-33818 →CVE-2026-42499 →CVE-2026-42504 →CVE-2026-56858 →CVE-2026-56860 →CVE-2026-56862 →CVE-2026-33811 →CVE-2026-39820 →CVE-2026-39821 →CVE-2026-56859 →

📋 Description

CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-33818 — encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal CVE-2026-39820 — net/mail: golang: Go net/mail: Denial of Service via crafted email inputs 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-42499 — net/mail: golang: net/mail: Denial of Service via pathological email address parsing CVE-2026-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header CVE-2026-56858 — html/template: golang: Go html/template: Cross-Site Scripting via pathological input CVE-2026-56859 — encoding/xml: golang: Go: Denial of Service via XML decoding recursion depth issue CVE-2026-56860 — net/url: golang: golang net/url: Denial of Service from quadratic complexity in path resolution CVE-2026-56862 — crypto/tls: golang: Golang crypto/tls: Denial of Service via indefinite KeyUpdate messages

🎯 Affected products74

  • Red Hat OpenShift Container Platform 4.19
  • cri-o-0:1.32.13-14.rhaos4.19.git3c1400a.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-0:1.32.13-14.rhaos4.19.git3c1400a.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-0:1.32.13-14.rhaos4.19.git3c1400a.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-0:1.32.13-14.rhaos4.19.git3c1400a.el9.src as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-0:1.32.13-14.rhaos4.19.git3c1400a.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debuginfo-0:1.32.13-14.rhaos4.19.git3c1400a.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debuginfo-0:1.32.13-14.rhaos4.19.git3c1400a.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debuginfo-0:1.32.13-14.rhaos4.19.git3c1400a.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debuginfo-0:1.32.13-14.rhaos4.19.git3c1400a.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debugsource-0:1.32.13-14.rhaos4.19.git3c1400a.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debugsource-0:1.32.13-14.rhaos4.19.git3c1400a.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debugsource-0:1.32.13-14.rhaos4.19.git3c1400a.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • cri-o-debugsource-0:1.32.13-14.rhaos4.19.git3c1400a.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy-0:2.8.10-3.rhaos4.19.el9.src as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy-debugsource-0:2.8.10-3.rhaos4.19.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy-debugsource-0:2.8.10-3.rhaos4.19.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy-debugsource-0:2.8.10-3.rhaos4.19.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy-debugsource-0:2.8.10-3.rhaos4.19.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-0:2.8.10-3.rhaos4.19.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-0:2.8.10-3.rhaos4.19.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-0:2.8.10-3.rhaos4.19.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-0:2.8.10-3.rhaos4.19.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-debuginfo-0:2.8.10-3.rhaos4.19.el9.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-debuginfo-0:2.8.10-3.rhaos4.19.el9.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-debuginfo-0:2.8.10-3.rhaos4.19.el9.s390x as a component of Red Hat OpenShift Container Platform 4.19
  • haproxy28-debuginfo-0:2.8.10-3.rhaos4.19.el9.x86_64 as a component of Red Hat OpenShift Container Platform 4.19
  • openshift-0:4.19.0-202609141900.p2.g63adf01.assembly.stream.el9.src as a component of Red Hat OpenShift Container Platform 4.19
  • openshift-clients-0:4.19.0-202609141900.p2.ga2c805b.assembly.stream.el8.aarch64 as a component of Red Hat OpenShift Container Platform 4.19
  • openshift-clients-0:4.19.0-202609141900.p2.ga2c805b.assembly.stream.el8.ppc64le as a component of Red Hat OpenShift Container Platform 4.19
  • +44 more not shown

✅ 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/ Workaround: To mitigate this issue, applications can be configured to use the pure Go DNS resolver instead of the `cgo` DNS resolver. This can be achieved by setting the `GODEBUG` environment variable to `netdns=go`. For example, to run a Go application with this mitigation: `GODEBUG=netdns=go /path/to/your/go/application`. This change may require restarting affected applications or services to take effect. Users should verify that this change does not negatively impact DNS resolution for their specific application environment. 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: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds. Workaround: To mitigate this issue, restrict network access to services that process MIME headers from untrusted sources. Implement input validation and sanitization for all incoming data, especially MIME headers, to prevent maliciously crafted content from being processed by applications utilizing the vulnerable Golang MIME package.

🔗 References (13)