Red Hat Security Advisory: host-metering security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2026-27145 — crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries
🎯 Affected products9
- Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-0:1.4.0-8.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-0:1.4.0-8.el7_9.src as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-0:1.4.0-8.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-debuginfo-0:1.4.0-8.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-debuginfo-0:1.4.0-8.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-debugsource-0:1.4.0-8.el7_9.ppc64le as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-debugsource-0:1.4.0-8.el7_9.x86_64 as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
- host-metering-selinux-0:1.4.0-8.el7_9.noarch as a component of Red Hat Enterprise Linux Server (v. 7 ELS)
✅ Remediation
For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 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).