OpenTelemetry's Zipkin remote endpoint cache could grow without bounds and increase memory pressure

中 5.3CVE-2026-41310 · GHSA-88hf-wf7h-7w4m · 06/05/2026 公開 · 26/10/2026 更新

要点

CVE-2026-41310 は OpenTelemetry.Exporter.Zipkin, opentelemetry.exporter.zipkin (opentelemetry) に影響する深刻度「中」 (CVSS 5.3) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.31%（全脆弱性の 24.0% より高い）。
対処：1.15.3 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
OpenTelemetry.Exporter.Zipkin NuGet	`< 1.15.3`	`1.15.3`
opentelemetry.exporter.zipkin opentelemetry	`< 1.15.3`	`1.15.3`

概要

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

NVD の説明

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.