RHSA-2026:51057HighCVSS 7.5

Red Hat Security Advisory: OpenShift Source To Image 1.6.3

Published
August 6, 2026
Last Modified
August 20, 2026

🔗 CVE IDs covered (5)

CVE-2026-41567 →CVE-2026-42306 →CVE-2026-42504 →CVE-2026-27145 →CVE-2026-33811 →

📋 Description

CVE-2026-27145 — crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries CVE-2026-33811 — net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME CVE-2026-41567 — docker: Moby/Docker Engine: Arbitrary Code Execution via malicious container image and compressed archive upload CVE-2026-42306 — github.com/docker/docker: github.com/moby/moby: Moby container framework: Host file overwrite via race condition in docker cp mount setup CVE-2026-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header

🎯 Affected products9

  • OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel8@sha256:165efe95829019cfa2262f929dce52ea95ff83ce495309726aad336fbdd5e346_amd64 as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel8@sha256:1fa54de6f9a2b2637715ba73efae4cd31eb2be55121ffdf33306d2cafc7cbdd3_ppc64le as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel8@sha256:3891a8717d05c5fd308ed4b3b09d53b793f5bddfadc365f7c07e597b5a14ce4d_arm64 as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel8@sha256:f3f19ccbae2990e1b0b5c366f880b1c1eb2a5f7515a4017f4fe6c9b089bf27d0_s390x as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel9@sha256:2a8a7fcaf8cb0acc0a2a66a46338887ca8a9823adc1d5fe29f2440560895ff7e_amd64 as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel9@sha256:c2321623908f1bbc2b353b7fd50cf30835511ef2715b00df1362edca3c8476a3_s390x as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel9@sha256:da07963beb33a34655d8aa1bf7c9b37b2c63d572d2689cf934243da5a2578573_ppc64le as a component of OpenShift Developer Tools and Services 1.6.3
  • registry.redhat.io/source-to-image/source-to-image-rhel9@sha256:fc22e7614d51d5a1f809cdea32979acec0e05361cdfd94ac773d269f473e6860_arm64 as a component of OpenShift Developer Tools and Services 1.6.3

✅ Remediation

It is recommended that existing users of OpenShift Source To Image upgrade to v1.6.3 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: 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, Red Hat recommends only running containers from trusted images. Additionally, users should avoid piping compressed archives into containers created from untrusted images. For environments utilizing authorization plugins, restricting access to the `PUT /containers/{id}/archive` endpoint can further reduce exposure. 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, 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 (8)