Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-88hf-wf7h-7w4m

MEDIUM

GHSA-88hf-wf7h-7w4m is a medium-severity (CVSS 5.3) Uncontrolled Resource Consumption vulnerability in OpenTelemetry.Exporter.Zipkin. O3 Security confirms whether GHSA-88hf-wf7h-7w4m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-41310
Published
Apr 28, 2026
Updated
May 8, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected
.NETOpenTelemetry.Exporter.Zipkin

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetOpenTelemetry.Exporter.Zipkinall versions1.15.3

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for OpenTelemetry.Exporter.Zipkin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update OpenTelemetry.Exporter.Zipkin to 1.15.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-88hf-wf7h-7w4m is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-88hf-wf7h-7w4m is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-88hf-wf7h-7w4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### 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/
O3 Security · Impact-Aware SCA

Is GHSA-88hf-wf7h-7w4m in your dependencies?

O3 detects GHSA-88hf-wf7h-7w4m across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.