CVE-2026-41078: OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path
open-telemetry · opentelemetry-dotnet
Affected: open-telemetry opentelemetry-dotnet · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 12% of scored CVEs
DescriptionCVE.org
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.
Affected products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- open-telemetry · opentelemetry-dotnet<= 1.6.0-rc.1
- open-telemetry · OpenTelemetry.Exporter.Jaeger<= 1.6.0-rc.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- open-telemetry
- Published
- April 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-41078 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.