OpenTelemetry's Zipkin remote endpoint cache could grow without bounds and increase memory pressure
Exact source revision recorded 23 Oct 2026 16:01:25 UTC. It does not establish the source's current position. Latest evidence.
osv · GHSA-88hf-wf7h-7w4m
Published### 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)
- Source published
- 28 Apr 2026 23:23:28 UTC
- Source modified
- 8 May 2026 19:51:02 UTC
- Observed here
- 23 Oct 2026 16:01:25 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
This view projects the publisher's source fields for reading; the original JSON retains additional fields and CVE enrichment containers. Attribution: osv · GitHub Advisory Database · CC-BY-4.0. Source text is retained; field grouping and change labels are provided by ChangeIntel.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
Publisher rating · MODERATE