open-telemetry opentelemetry-go up to 1.42.x Configured Collector Endpoint traces/metrics/logs memory allocation

Summaryinfo

A vulnerability was found in open-telemetry opentelemetry-go up to 1.42.x and classified as problematic. The affected element is an unknown function of the file traces/metrics/logs of the component Configured Collector Endpoint. The manipulation results in memory allocation. This vulnerability is reported as CVE-2026-39882. The attacker must have access to the local network to execute the attack. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in open-telemetry opentelemetry-go up to 1.42.x. Affected is an unknown code of the file traces/metrics/logs of the component Configured Collector Endpoint. The manipulation with an unknown input leads to a memory allocation vulnerability. CWE is classifying the issue as CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. This is going to have an impact on availability. CVE summarizes:

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2026-39882 since 04/07/2026. The exploitability is told to be difficult. The attack needs to be initiated within the local network. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 305793 (Linux Distros Unpatched Vulnerability : CVE-2026-39882), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.43.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the databases at Tenable (305793) and CERT Bund (WID-SEC-2026-2334). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Affected

• Red Hat Enterprise Linux
• Red Hat OpenShift
• Splunk Splunk Enterprise

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-go

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.29
• 1.30
• 1.31
• 1.32
• 1.33
• 1.34
• 1.35
• 1.36
• 1.37
• 1.38
• 1.39
• 1.40
• 1.41
• 1.42

Website

• Product: https://github.com/open-telemetry/opentelemetry-go/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion