open-telemetry opentelemetry-dotnet-contrib up to 0.1.0-alpha.7 Sampling Endpoint ReadAsStringAsync allocation of resources

Summaryinfo

A vulnerability, which was classified as problematic, was found in open-telemetry opentelemetry-dotnet-contrib up to 0.1.0-alpha.7. The affected element is the function ReadAsStringAsync of the component Sampling Endpoint. Executing a manipulation can lead to allocation of resources. This vulnerability is registered as CVE-2026-41173. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic was found in open-telemetry opentelemetry-dotnet-contrib up to 0.1.0-alpha.7. This vulnerability affects the function ReadAsStringAsync of the component Sampling Endpoint. The manipulation with an unknown input leads to a allocation of resources vulnerability. The CWE definition for the vulnerability is CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. As an impact it is known to affect availability. CVE summarizes:

The AWS X-Ray Remote Sampler package provides a sampler which can get sampling configurations from AWS X-Ray. Prior to 0.1.0-alpha.8, OpenTelemetry.Sampler.AWS reads unbounded HTTP response bodies from a configured AWS X-Ray remote sampling endpoint into memory. AWSXRaySamplerClient.DoRequestAsync called HttpClient.SendAsync followed by ReadAsStringAsync(), which materializes the entire HTTP response body into a single in-memory string with no size limit. The sampling endpoint is configurable via AWSXRayRemoteSamplerBuilder.SetEndpoint (default: http://localhost:2000). An attacker who controls the configured endpoint, or who can intercept traffic to it (MitM), can return an arbitrarily large response body. This causes unbounded heap allocation in the consuming process, leading to high transient memory pressure, garbage-collection stalls, or an OutOfMemoryException that terminates the process. This vulnerability is fixed in 0.1.0-alpha.8.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-41173 since 04/17/2026. The exploitation appears to be difficult. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1499.

Upgrading to version 0.1.0-alpha.8 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 vulnerability database at EUVD (EUVD-2026-25271). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-dotnet-contrib

Version

• 0.1.0-alpha.0
• 0.1.0-alpha.1
• 0.1.0-alpha.2
• 0.1.0-alpha.3
• 0.1.0-alpha.4
• 0.1.0-alpha.5
• 0.1.0-alpha.6
• 0.1.0-alpha.7

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

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

Discussion