open-telemetry opentelemetry-dotnet/OpenTelemetry.Exporter.Jaeger allocation of resources

Summaryinfo

A vulnerability has been found in open-telemetry opentelemetry-dotnet and OpenTelemetry.Exporter.Jaeger up to 1.6.0-rc.1 and classified as problematic. The impacted element is an unknown function. The manipulation leads to allocation of resources. This vulnerability is documented as CVE-2026-41078. The attack can be initiated remotely. There is not any exploit available.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in open-telemetry opentelemetry-dotnet and OpenTelemetry.Exporter.Jaeger up to 1.6.0-rc.1. This issue affects an unknown part. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to 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. Impacted is availability. The summary by CVE is:

OpenTelemetry dotnet is a dotnet telemetry framework. In 1.6.0-rc.1 and earlier, OpenTelemetry.Exporter.Jaeger may allow sustained memory pressure when the internal pooled-list sizing grows based on a large observed span/tag set and that enlarged size is reused for subsequent allocations. Under high-cardinality or attacker-influenced telemetry input, this can increase memory consumption and potentially cause denial of service. There is no plan to fix this issue as OpenTelemetry.Exporter.Jaeger was deprecated in 2023.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-41078 since 04/16/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. MITRE ATT&CK project uses the attack technique T1499 for this issue.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

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

Productinfo

Vendor

• open-telemetry

Name

• opentelemetry-dotnet
• OpenTelemetry.Exporter.Jaeger

Version

• 1.6.0-rc.0
• 1.6.0-rc.1

Website

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

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