open-telemetry opentelemetry-dotnet-contrib up to 1.15.0 HttpJsonPostTransport allocation of resources

Summaryinfo

A vulnerability classified as problematic was found in open-telemetry opentelemetry-dotnet-contrib up to 1.15.0. This affects the function HttpJsonPostTransport. Executing a manipulation can lead to allocation of resources. This vulnerability is tracked as CVE-2026-41484. The attack is only possible within the local network. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in open-telemetry opentelemetry-dotnet-contrib up to 1.15.0 and classified as problematic. This vulnerability affects the function HttpJsonPostTransport. 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:

OpenTelemetry.Exporter.OneCollector is a .NET exporter that sends telemetry to a OneCollector back-end over HTTP. In versions 1.15.0 and earlier, when a request to the configured back-end or collector results in an unsuccessful HTTP 4xx or 5xx response, the HttpJsonPostTransport class reads the entire response body into memory with no upper bound on the number of bytes consumed in order to include the error response in operator logs. An attacker who controls the configured endpoint, or who can intercept traffic to it via a man-in-the-middle attack, 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. As a workaround, use network-level controls such as firewall rules, mTLS, or a service mesh to prevent man-in-the-middle attacks on the configured back-end or collector endpoint. This issue is fixed in version 1.15.1, which limits the number of bytes read from the response body in an error condition to 4 MiB.

The advisory is shared for download at github.com. This vulnerability was named CVE-2026-41484 since 04/20/2026. The exploitation appears to be difficult. The attack needs to approached within the local network. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.

Upgrading 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.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-dotnet-contrib

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.0

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

Once again VulDB remains the best source for vulnerability data.

Discussion