https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-10T17:08:23.366701+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/euvd-2026-308974 EUVD-2026-308974 2026-10-10T17:08:23.368841+00:00 EUVD-2026-308974 https://cve.radiocsirt.org/vuln/fkie_cve-2026-41310 fkie_cve-2026-41310 2026-10-10T17:08:23.368873+00:00

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.

 https://cve.radiocsirt.org/vuln/ghsa-88hf-wf7h-7w4m GHSA-88hf-wf7h-7w4m — OpenTelemetry's Zipkin remote endpoint cache could grow without bounds and increase memory pressure 2026-10-10T17:08:23.368905+00:00

Affected: NuGet: OpenTelemetry.Exporter.Zipkin

### Summary

The Zipkin exporter remote endpoint cache accepted unbounded key growth derived from span attributes. In high-cardinality scenarios, this could increase process memory usage over time and degrade availability.

### Details

- Introduce a bounded, thread-safe LRU cache for remote endpoints. - Enforce fixed maximum size to prevent unbounded growth.

### Impact

- A process using Zipkin export for client/producer spans could experience avoidable memory growth under sustained unique remote endpoint values.

### Resources

[#7081](https://github.com/open-telemetry/opentelemetry-dotnet/pull/7081)