RHSA-2026:50205HighCVSS 7.5

Red Hat Security Advisory: Red Hat build of OpenTelemetry 3.10.1 release

Published
August 4, 2026
Last Modified
August 20, 2026

🔗 CVE IDs covered (13)

CVE-2026-54369 →CVE-2026-5435 →CVE-2026-5450 →CVE-2026-27145 →CVE-2026-42504 →CVE-2026-54370 →CVE-2025-5278 →CVE-2026-5928 →CVE-2026-33811 →CVE-2026-33814 →CVE-2026-39820 →CVE-2026-39823 →CVE-2026-42507 →

📋 Description

CVE-2025-5278 — coreutils: Heap Buffer Under-Read in GNU Coreutils sort via Key Specification CVE-2026-5435 — glibc: glibc: Out-of-bounds write via TSIG record processing CVE-2026-5450 — glibc: glibc: Heap Buffer Overflow in scanf with %mc format specifier and large width CVE-2026-5928 — glibc: glibc: Information disclosure or denial of service via ungetwc function with specific wide character encodings 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-33814 — net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame CVE-2026-39820 — net/mail: golang: Go net/mail: Denial of Service via crafted email inputs CVE-2026-39823 — html/template: golang: Go html/template: Cross-Site Scripting via improper URL escaping in meta tag content CVE-2026-42504 — mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header CVE-2026-42507 — net/textproto: golang: Golang net/textproto: Misleading error messages via input injection CVE-2026-54369 — acl: Symlink traversal privilege escalation via libacl functions CVE-2026-54370 — acl: TOCTOU Symlink Traversal via getfacl/setfacl

🎯 Affected products14

  • Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:03fd3e2921ac7557fd5aa6b4d0714f9ee634efd1259b789638d478978fcd4f39_s390x as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:4873d91250b9fad16135ca6b4b34fce6da9919a6a31dca517be3535b6a436595_arm64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:73720c25cac560d195b72d0a504ba259df85eb90f1d846bfe63138632409f3f3_amd64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:a14ce218cde5a6aade253140ed32557f408eaf2abc61d41218cc566a9ddd3737_ppc64le as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-operator-bundle@sha256:356d387d225f1d73142d8ce3fb50086e4412c84313a2707032fdfc9c7ba4ab03_amd64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:03af0af704f201e97cc36cb588092366e613a26794d25ec76d805f0de00fbb77_amd64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:12db5b608310ed1c220e5424469899bdf7d704912d86bc4500e7d8f0b75953a9_s390x as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:589887e35b27614cf2c9749377ffafe41e4280b2738dbc76ce8f67c13244a86f_arm64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:75a06c4af8c69609f32ea93e4af91f4b7b244586bc9bec314e826772bec58bf2_ppc64le as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:2cdd8292273cb748f58949b053a5d2f104d30bcf91f28ec62a0d3b6e864e6c11_ppc64le as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:31162741b966e9106e72c097e61d64e713adb2fb04d3881be326118a98f77b09_amd64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:79a1d157a3b9e7130653068bd30b2bab7f27c8fd669e604594b69dc230e4b80f_arm64 as a component of Red Hat OpenShift distributed tracing 3.10.1
  • registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:a67bdb7df46656eaedc60de5d86fa62f6a16e7b157bd34575f2926c04e9a311f_s390x as a component of Red Hat OpenShift distributed tracing 3.10.1

✅ Remediation

For details on how to apply this update, refer to: https://docs.redhat.com/en/documentation/openshift_container_platform/latest/html/operators/administrator-tasks#olm-upgrading-operators Workaround: Mitigation for this issue is either not available or the currently available options don't meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. 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: 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: Ensure that user-supplied URLs are validated and sanitized before being passed to Go's `html/template` package for rendering in HTML meta tag content attributes. Avoid rendering untrusted URL data directly in meta tag content attributes. 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. Workaround: Restrict unprivileged users from creating symlinks in directories that privileged processes operate on with ACL commands. Where possible, use the fs.protected_symlinks sysctl (enabled by default on RHEL 7+), which prevents symlink following in world-writable sticky directories unless the owner of the symlink matches the owner of the target file or directory.

🔗 References (17)