RHSA-2026:42048HighCVSS 8.2

Red Hat Security Advisory: Red Hat Web Terminal Operator 1.16.1 release.

Published
July 20, 2026
Last Modified
September 14, 2026

🔗 CVE IDs covered (5)

CVE-2026-32281 →CVE-2026-32282 →CVE-2026-33811 →CVE-2026-39821 →CVE-2026-42504 →

📋 Description

CVE-2026-32281 — crypto/x509: golang: Go crypto/x509: Denial of Service via inefficient certificate chain validation CVE-2026-32282 — golang: internal/syscall/unix: Root.Chmod can follow symlinks out of the root CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME 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-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header

🎯 Affected products5

  • Red Hat Web Terminal 1.16
  • registry.redhat.io/web-terminal/web-terminal-exec-rhel9@sha256:365e1253b8da2ba88ec97ec5b074d16ac46b31fd7eba3baad6587ce8959b11bf_amd64 as a component of Red Hat Web Terminal 1.16
  • registry.redhat.io/web-terminal/web-terminal-operator-bundle@sha256:25e450ef9a1bbdb5e6d522a98928c0784c483de40f17ee111e8c32e59c4e78c9_amd64 as a component of Red Hat Web Terminal 1.16
  • registry.redhat.io/web-terminal/web-terminal-rhel9-operator@sha256:f331222fc180e7195d51536dab01692da66ad9049671e034867855dce1e5b656_amd64 as a component of Red Hat Web Terminal 1.16
  • registry.redhat.io/web-terminal/web-terminal-tooling-rhel9@sha256:fefa9980c5021706ccac27d05086359f45109790089e586221c08271b55b1b25_amd64 as a component of Red Hat Web Terminal 1.16

✅ Remediation

To start using the Web Terminal Operator, install the Web Terminal Operator from OpenShift OperatorHub on OpenShift Container Platform 4.21 or higher. 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: 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)