open-telemetry opentelemetry-dotnet-contrib up to 0.2.0-alpha.0 OpenTelemetry.OpAmp.Client memory allocation

Summaryinfo

A vulnerability identified as problematic has been detected in open-telemetry opentelemetry-dotnet-contrib up to 0.2.0-alpha.0. The affected element is an unknown function of the component OpenTelemetry.OpAmp.Client. The manipulation leads to memory allocation. This vulnerability is documented as CVE-2026-42348. The attack can be initiated remotely. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in open-telemetry opentelemetry-dotnet-contrib up to 0.2.0-alpha.0 and classified as problematic. This issue affects some unknown functionality of the component OpenTelemetry.OpAmp.Client. The manipulation with an unknown input leads to a memory allocation vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:

OpenTelemetry.OpAmp.Client is the OpAMP client for OpenTelemetry .NET. Prior to 0.2.0-alpha.1, when receiving responses from the OpAMP server over HTTP, the OpAMP client allocates an unbounded buffer to read all bytes from the server, with no upper-bound on the number of bytes consumed. This could cause memory exhaustion in the consuming application if the configured OpAMP server is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned in the response. This vulnerability is fixed in 0.2.0-alpha.1.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-42348 since 04/26/2026. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.2.0-alpha.1 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.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-dotnet-contrib

Version

• 0.2.0-alpha

Website

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

CPE 2.3info

• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion