CVE-2026-41310: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-dotnet
OpenTelemetry.Exporter.Zipkin is the .NET Zipkin exporter for OpenTelemetry. In versions 1.15.2 and earlier, the Zipkin exporter remote endpoint cache accepts unbounded key growth derived from span attributes. In high-cardinality scenarios, a process using Zipkin export for client or producer spans could experience avoidable memory growth under sustained unique remote endpoint values, increasing process memory usage over time and degrading availability. This issue is fixed in version 1.15.3, which introduces a bounded, thread-safe LRU cache for remote endpoints with a fixed maximum size.
AI Analysis
Technical Summary
The OpenTelemetry.Exporter.Zipkin component in opentelemetry-dotnet versions up to 1.15.2 has a resource allocation vulnerability (CWE-770) where the remote endpoint cache grows without bounds when processing span attributes with high cardinality. This unbounded cache growth can lead to increased memory usage over time, impacting process stability and availability. The vulnerability is addressed in version 1.15.3 by implementing a fixed-size, thread-safe LRU cache to limit memory consumption.
Potential Impact
This vulnerability can cause a process using the Zipkin exporter to consume increasing amounts of memory under sustained high-cardinality remote endpoint values, potentially leading to degraded availability or process instability. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
A fix is available in opentelemetry-dotnet version 1.15.3, which introduces a bounded, thread-safe LRU cache to prevent unbounded memory growth. Users should upgrade to version 1.15.3 or later to remediate this issue. Patch status is not explicitly stated in the vendor advisory content provided, but the description confirms the fix is implemented in 1.15.3.
CVE-2026-41310: CWE-770: Allocation of Resources Without Limits or Throttling in open-telemetry opentelemetry-dotnet
Description
OpenTelemetry.Exporter.Zipkin is the .NET Zipkin exporter for OpenTelemetry. In versions 1.15.2 and earlier, the Zipkin exporter remote endpoint cache accepts unbounded key growth derived from span attributes. In high-cardinality scenarios, a process using Zipkin export for client or producer spans could experience avoidable memory growth under sustained unique remote endpoint values, increasing process memory usage over time and degrading availability. This issue is fixed in version 1.15.3, which introduces a bounded, thread-safe LRU cache for remote endpoints with a fixed maximum size.
CVSS v3.1
Score 5.3medium
Affected software
pkg:nuget/opentelemetry.exporter.zipkinRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The OpenTelemetry.Exporter.Zipkin component in opentelemetry-dotnet versions up to 1.15.2 has a resource allocation vulnerability (CWE-770) where the remote endpoint cache grows without bounds when processing span attributes with high cardinality. This unbounded cache growth can lead to increased memory usage over time, impacting process stability and availability. The vulnerability is addressed in version 1.15.3 by implementing a fixed-size, thread-safe LRU cache to limit memory consumption.
Potential Impact
This vulnerability can cause a process using the Zipkin exporter to consume increasing amounts of memory under sustained high-cardinality remote endpoint values, potentially leading to degraded availability or process instability. There is no impact on confidentiality or integrity, only availability is affected.
Mitigation Recommendations
A fix is available in opentelemetry-dotnet version 1.15.3, which introduces a bounded, thread-safe LRU cache to prevent unbounded memory growth. Users should upgrade to version 1.15.3 or later to remediate this issue. Patch status is not explicitly stated in the vendor advisory content provided, but the description confirms the fix is implemented in 1.15.3.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-20T14:01:46.670Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69fbb106cbff5d8610650ae3
Added to database: 05/06/2026, 21:22:14 UTC
Last enriched: 05/14/2026, 03:50:40 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 117
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.