RHSA-2026:90329HighCVSS 8.2

Red Hat Security Advisory: Red Hat OpenStack Platform 17.1 security advisory

Published
October 26, 2026
Last Modified
November 3, 2026

🔗 CVE IDs covered (15)

CVE-2026-73500 →CVE-2026-27145 →CVE-2026-32280 →CVE-2026-33818 →CVE-2026-39821 →CVE-2026-56862 →CVE-2026-78669 →CVE-2026-32283 →CVE-2026-56858 →CVE-2026-111943 →CVE-2026-25679 →CVE-2026-33811 →CVE-2026-56853 →CVE-2026-56860 →CVE-2025-61726 →

📋 Description

CVE-2025-61726 — golang: net/url: Memory exhaustion in query parameter parsing in net/url CVE-2026-25679 — net/url: Incorrect parsing of IPv6 host literals in net/url CVE-2026-27145 — crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries CVE-2026-32280 — crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building 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-39821 — golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing 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-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-73500 — etcd: etcd: Denial of Service via unbounded TLS handshake goroutines CVE-2026-78669 — net/http: net/http/internal/http2: golang.org/x/net/http2: net/http: Denial of Service via excessive HTTP/2 SETTINGS frames CVE-2026-111943 — crypto/x509: golang: crypto/x509: Man-in-the-middle attacks via untrusted intermediate certificates

🎯 Affected products10

  • Red Hat OpenStack Platform 17.1
  • collectd-libpod-stats-0:1.0.6-9.el9ost.src as a component of Red Hat OpenStack Platform 17.1
  • collectd-libpod-stats-0:1.0.6-9.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1
  • collectd-sensubility-0:0.2.1-8.el9ost.src as a component of Red Hat OpenStack Platform 17.1
  • collectd-sensubility-0:0.2.1-8.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1
  • collectd-sensubility-debuginfo-0:0.2.1-8.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1
  • etcd-0:3.4.26-9.10.el9ost.src as a component of Red Hat OpenStack Platform 17.1
  • etcd-0:3.4.26-9.10.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1
  • etcd-debuginfo-0:3.4.26-9.10.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1
  • etcd-debugsource-0:3.4.26-9.10.el9ost.x86_64 as a component of Red Hat OpenStack Platform 17.1

✅ Remediation

Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258 Workaround: Red Hat has investigated whether a possible mitigation exists for this issue, and has not been able to identify a practical example. Please update the affected package as soon as possible. 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: 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: Upgrade to a fixed golang.org/x/net release that includes the idna correction, via updated golang or dependent package rebuilds. Workaround: Restrict network access to the etcd TLS listener to only trusted clients and networks. Configure firewall rules to limit inbound connections to the etcd client port (default 2379) and peer port (default 2380) to authorized hosts. This reduces the attack surface by preventing untrusted network attackers from reaching the vulnerable service. Workaround: In case you consume HTTP2, upgrade to a patched version of the http module. Verify: ``` go version go list -m golang.org/x/net govulncheck ./... ``` Workaround: See the security bulletin for a detailed mitigation procedure.

🔗 References (18)