RHSA-2026:19135HighCVSS 9.1

Red Hat Security Advisory: opentelemetry-collector security update

Published
May 19, 2026
Last Modified
August 15, 2026

🔗 CVE IDs covered (8)

CVE-2026-34986 →CVE-2026-25679 →CVE-2026-32280 →CVE-2026-32281 →CVE-2026-32282 →CVE-2026-32283 →CVE-2026-33186 →CVE-2026-33810 →

📋 Description

CVE-2026-25679 — net/url: Incorrect parsing of IPv6 host literals in net/url CVE-2026-32280 — crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building 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-32283 — crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages CVE-2026-33186 — google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation CVE-2026-33810 — crypto/x509: golang: Go crypto/x509: Certificate validation bypass due to incorrect DNS constraint application CVE-2026-34986 — github.com/go-jose/go-jose/v3: github.com/go-jose/go-jose/v4: Go JOSE: Denial of Service via crafted JSON Web Encryption (JWE) object

🎯 Affected products6

  • Red Hat Enterprise Linux AppStream (v. 10)
  • opentelemetry-collector-0:0.144.0-2.el10_2.aarch64 as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • opentelemetry-collector-0:0.144.0-2.el10_2.ppc64le as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • opentelemetry-collector-0:0.144.0-2.el10_2.s390x as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • opentelemetry-collector-0:0.144.0-2.el10_2.src as a component of Red Hat Enterprise Linux AppStream (v. 10)
  • opentelemetry-collector-0:0.144.0-2.el10_2.x86_64 as a component of Red Hat Enterprise Linux AppStream (v. 10)

✅ 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: 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, implement infrastructure-level normalization to ensure all incoming HTTP/2 `:path` headers are properly formatted with a leading slash before reaching the gRPC-Go server. This can be achieved by configuring a reverse proxy or API gateway to validate and normalize the `:path` header. Ensure that any such intermediary is properly configured and restarted to apply the changes, which may temporarily impact service availability.

🔗 References (11)