- Issued:
- 2026-05-06
- Updated:
- 2026-05-06
RHSA-2026:14162 - Security Advisory
Synopsis
Red Hat build of OpenTelemetry 3.9.3 release
Type/Severity
Security Advisory: Important
Topic
Red Hat build of OpenTelemetry 3.9.3 has been released
Description
This release of the Red Hat build of OpenTelemetry provides security improvements.
Breaking changes:
- None
Deprecations:
- None
Technology Preview features:
- None
Enhancements:
- None
Bug fixes:
- TOCTOU race condition in libcap cap_set_file() function is fixed. Previously, the cap_set_file() function in libcap contained a Time-of-check-to-time-of-use (TOCTOU) race condition. A local unprivileged user with write access to a parent directory could exploit this vulnerability to redirect file capability updates to an attacker-controlled file. This flaw allowed an attacker to inject capabilities into or strip capabilities from unintended executables, leading to privilege escalation. With this update, the race condition in cap_set_file() is fixed. As a result, file capability updates are applied to the intended target files, and the vulnerability is no longer exploitable. For more information, see https://access.redhat.com/security/cve/CVE-2026-4878.
- Integer overflow vulnerability in Apache Thrift TFramedTransport Go implementation is fixed. Previously, the Apache Thrift TFramedTransport Go language implementation contained an integer overflow or wraparound vulnerability. An attacker could exploit this flaw to cause unexpected behavior or resource exhaustion, leading to a denial of service. With this update, the integer overflow issue is fixed. As a result, TFramedTransport correctly handles integer values, and the vulnerability is no longer exploitable. For more information, see https://access.redhat.com/security/cve/CVE-2026-41602.
- Denial of service vulnerability in Go crypto/x509 and crypto/tls packages is fixed. Previously, the Go standard library packages crypto/x509 and crypto/tls did not properly limit the number of intermediate certificates processed during certificate chain building. An attacker could provide an excessive number of intermediate certificates, causing an uncontrolled amount of work. This flaw could result in a denial of service (DoS) condition, making the affected system or application unavailable to legitimate users. With this update, the number of intermediate certificates processed during certificate chain building is properly limited. As a result, the packages handle certificate chains efficiently, and the vulnerability is no longer exploitable. For more information, see https://access.redhat.com/security/cve/CVE-2026-32280.
- TLS 1.3 connection deadlock vulnerability is fixed. Previously, if one side of a TLS 1.3 connection sent multiple key update messages post-handshake in a single record, the connection could deadlock. This deadlock caused uncontrolled consumption of resources and could lead to a denial of service. With this update, TLS 1.3 connections correctly handle multiple key update messages in a single record. As a result, connections no longer deadlock, and the vulnerability is no longer exploitable. For more information about CVE-2026-32283, see https://groups.google.com/g/golang-announce/c/0uYbvbPZRWU.
- IPC API vulnerability in systemd is fixed. Previously, system and service manager systemd contained a flaw that an unprivileged user could exploit by making an Inter-Process Communication (IPC) API call with spurious data. In older versions (v249 and earlier), this flaw could lead to stack overwriting with attacker-controlled content, potentially enabling arbitrary code execution or privilege escalation. In newer versions (v250 and later), this flaw caused systemd to assert and freeze, resulting in a denial of service (DoS). With this update, systemd correctly validates IPC API calls. As a result, the vulnerability is no longer exploitable. For more information, see https://access.redhat.com/security/cve/CVE-2026-29111.
Known issues:
- The filesystem scraper does not produce the system.filesystem.inodes.usage and system.filesystem.usage metrics in the Host Metrics Receiver after upgrading from Collector version 0.142.0 to 0.143.0 or later. No known workaround exists. For more information, see https://issues.redhat.com/browse/TRACING-5963.
Solution
For details on how to apply this update, refer to:
Fixes
(none)amd64
| registry.redhat.io/rhosdt/opentelemetry-operator-bundle@sha256:736f03edb0dfea64fcb9a723dc8a01d8ffd4f2c5b952b3a8f1b2ab6b7320af4b |
| registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:5adac8b8aa26beaa38c4a0d20f0271890c0fbaf06b9bcbc7c00a3e27cd1a4c5b |
| registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:a12ee44613f8bb32f083f719b08af74a8e72815ab35156cb23242f2889745865 |
| registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:c8348d21a8cecefea08d43a4bcd4898bc086ce91ccd60a2e9c31bbb13e5511c7 |
arm64
| registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:3485dd7a7615da6e658547c117818f41c855aa8fcff80b609e56afec46e00546 |
| registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:fcd49001027e05749fd68dadc316af46bd7d49931821950cbeb037c7d19f7d66 |
| registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:c87072639a6a332398c6681de4f18578c4778f33117e25be63fca278bb94ab2b |
ppc64le
| registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:36790acac3369dd38803aca4433376edfa9edc8785ea0b61ec95b931effddf00 |
| registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:d52121422c85bc4b79590e67bf047d90b50b763425fcf5676265f65eb3faa1e2 |
| registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:676693e80ea746f3e6382a0cd81b21c77c3922cafa74ec3a349b89943d59f2ee |
s390x
| registry.redhat.io/rhosdt/opentelemetry-collector-rhel9@sha256:265d8d864589e9ca6739e5eff46be545dc531aa6aa72378674b3ae9ff48f14ac |
| registry.redhat.io/rhosdt/opentelemetry-rhel9-operator@sha256:109f44564a590b7dbdf7337f93a5297875f58e2810123a134a5386a5ba8bd62b |
| registry.redhat.io/rhosdt/opentelemetry-target-allocator-rhel9@sha256:a2d150f31c8e11e4d0cc651d8a58212f769d00b453e6a7efcc68ca5cca63878d |
The Red Hat security contact is secalert@redhat.com. More contact details at https://access.redhat.com/security/team/contact/.