RHSA-2026:95206HighCVSS 8.1

Red Hat Security Advisory: Updated Red Hat OpenStack Platform 16.2 director Operator container images

Published
November 4, 2026
Last Modified
November 14, 2026

🔗 CVE IDs covered (11)

CVE-2026-32283 →CVE-2026-33811 →CVE-2026-33818 →CVE-2026-56853 →CVE-2026-56859 →CVE-2026-56860 →CVE-2026-27145 →CVE-2026-42504 →CVE-2026-56858 →CVE-2026-56862 →CVE-2026-111943 →

📋 Description

CVE-2026-27145 — crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries CVE-2026-32283 — crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages 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-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header CVE-2026-56853 — net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service 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 CVE-2026-111943 — crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates

🎯 Affected products5

  • Red Hat OpenStack Platform 16.2
  • registry.redhat.io/rhosp-rhel8/osp-director-agent@sha256:71db0458b0db758d312e2d2cb59013bb0e79fa0c7ae06c7b0e386ae0db82d220_amd64 as a component of Red Hat OpenStack Platform 16.2
  • registry.redhat.io/rhosp-rhel8/osp-director-downloader@sha256:79c9d15266c7e500af924b8aed0cf6d53eae1ae9f516d05548031249001e5b65_amd64 as a component of Red Hat OpenStack Platform 16.2
  • registry.redhat.io/rhosp-rhel8/osp-director-operator-bundle@sha256:0adbe2c93819ef7c63bbf02b6acd6a09936dae526dff125f706cce87bfff804c_amd64 as a component of Red Hat OpenStack Platform 16.2
  • registry.redhat.io/rhosp-rhel8/osp-director-operator@sha256:8ccad88a3718868dd2f75e7bc421db851129ea90e9e612e04d204daecac431cb_amd64 as a component of Red Hat OpenStack Platform 16.2

✅ Remediation

The container images provided by this update can be downloaded from the Red Hat container registry at registry.redhat.io or registry.access.redhat.com using the 'podman pull' command. For more information about the images, search the image name in the Red Hat Ecosystem Catalog. Workaround: A flaw was found in the Go standard library crypto/x509 package. When verifying a TLS certificate hostname, VerifyHostname processed each DNS Subject Alternative Name (SAN) entry in a loop and repeatedly split the candidate hostname on "." characters. For certificates with a very large DNS SAN list, CPU use could grow quadratically with the number of SAN entries and hostname labels. Because hostname verification runs before the certificate chain is built, this overhead can occur even when the certificate is not trusted. Red Hat rates this issue as Important. It affects Red Hat products that include the Go standard library crypto/x509 code from an affected Go toolchain version (before Go 1.25.11, or from Go 1.26.0 through Go 1.26.3). Applications and container images built with a fixed Go release (1.25.11 or later, or 1.26.4 or later) are not affected. Community distributions such as Fedora are also affected. Upstream fix: Go 1.25.11 and Go 1.26.4 (GO-2026-5037). 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, 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: 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. Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (15)