RHSA-2026:80684HighCVSS 8.1

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

Published
October 12, 2026
Last Modified
October 14, 2026

🔗 CVE IDs covered (13)

CVE-2026-56860 →CVE-2026-56862 →CVE-2026-32283 →CVE-2026-33818 →CVE-2026-56853 →CVE-2026-56858 →CVE-2026-56859 →CVE-2026-27145 →CVE-2026-33811 →CVE-2026-39829 →CVE-2026-39830 →CVE-2026-42504 →CVE-2026-46597 →

📋 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-39829 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted public key with excessive parameters CVE-2026-39830 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via resource leak from unsolicited SSH responses CVE-2026-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header CVE-2026-46597 — golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via crafted AES-GCM packet decoder inputs 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

🎯 Affected products5

  • Red Hat OpenStack Platform 17.1
  • registry.redhat.io/rhosp-rhel9/osp-director-agent@sha256:6137209995c857c10d1b7d55eafaa32dd14fef224f575e71f912eab28a76bbbb_amd64 as a component of Red Hat OpenStack Platform 17.1
  • registry.redhat.io/rhosp-rhel9/osp-director-downloader@sha256:b4a5620ca7a228bd175b53a1dd8116b47bfb16460c628318382feeeb46c7bee9_amd64 as a component of Red Hat OpenStack Platform 17.1
  • registry.redhat.io/rhosp-rhel9/osp-director-operator-bundle@sha256:6baa13d985ef1ff6f08399cc2ef04832e23982472bfdede2a7acd9a4b559c637_amd64 as a component of Red Hat OpenStack Platform 17.1
  • registry.redhat.io/rhosp-rhel9/osp-director-operator@sha256:c451fd722d0eed3d2a416fe66d9852310b585e7fa7cacb24675a6c06ee30d9d6_amd64 as a component of Red Hat OpenStack Platform 17.1

✅ 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 denial of service vulnerability, restrict network access to any service that utilizes the `golang.org/x/crypto/ssh` library and is exposed to untrusted networks. Implement firewall rules to allow connections only from trusted hosts or networks. This action limits the ability of malicious peers to send unsolicited global request responses. A restart of the affected service may be necessary for the new network rules to be applied effectively. 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 (17)