CVE-2026-41078: OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path
Summary
> [!IMPORTANT] > There is no plan to fix this issue as OpenTelemetry.Exporter.Jaeger was deprecated in 2023. It is for informational purposes only.
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.
Details
The Jaeger exporter conversion path can append tag/event data into pooled list structures. In affected versions, pooled allocation sizing may be influenced by large observed payloads and reused globally across later allocations, resulting in persistent oversized rentals and elevated memory pressure. In environments where telemetry attributes/events can be influenced by untrusted input and limits are increased from defaults, this may lead to process instability or denial of service.
Impact
Availability impact only. Confidentiality and integrity impacts are not expected.
Workarounds / Mitigations
Prefer maintained exporters (for example OpenTelemetry Protocol format (OTLP)) instead of the Jaeger exporter.
Other sources
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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-41078?
The CVE-2026-41078 vulnerability does not have a severity rating as it is informational only.
How do I fix CVE-2026-41078?
There is no fix for CVE-2026-41078 as OpenTelemetry.Exporter.Jaeger has been deprecated since 2023.
What impact does CVE-2026-41078 have on my application?
CVE-2026-41078 may cause sustained memory pressure due to internal pooled-list sizing in OpenTelemetry.Exporter.Jaeger.
Which versions of OpenTelemetry are affected by CVE-2026-41078?
CVE-2026-41078 affects OpenTelemetry.Exporter.Jaeger version 1.6.0-rc.1 and below.
Is there a recommended alternative to OpenTelemetry.Exporter.Jaeger due to CVE-2026-41078?
Consider using other supported OpenTelemetry exporters, as OpenTelemetry.Exporter.Jaeger has been deprecated.