OpenTelemetry .NET是OpenTelemetry公司的OpenTelemetry的.NET客户端。 OpenTelemetry .NET存在安全漏洞,该漏洞源于baggage、B3和Jaeger处理代码实现细节,可能导致解析时分配过多内存,造成拒绝服务。以下产品及版本受到影响:OpenTelemetry.Api 0.5.0-beta.2版本至1.15.2版本和OpenTelemetry.Extensions.Propagators 1.3.1版本至1.15.2版本。
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| open-telemetry | opentelemetry-dotnet | >= 0.5.0-beta.2, < 1.15.3 | - |
|
| open-telemetry | OpenTelemetry.Api | >= 0.5.0-beta.2, < 1.15.3 | - |
|
| open-telemetry | OpenTelemetry.Extensions.Propagators | >= 1.3.1, < 1.15.3 | - |
|
| # | POC Description | Source Link | Shenlong Link |
|---|
No public POC found.
Login to generate AI POC| CVE-2026-41078 | 5.9 MEDIUM | OpenTelemetry dotnet: Potential memory exhaustion via unbounded pooled-list sizing in Jaeg |
| CVE-2026-41173 | 5.9 MEDIUM | Unbounded HTTP response body read in OpenTelemetry.Sampler.AWS |
| CVE-2026-40182 | 5.3 MEDIUM | OpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies |
| CVE-2026-40891 | 5.3 MEDIUM | OpenTelemetry dotnet: Unbounded `grpc-status-details-bin` parsing in OTLP/gRPC retry handl |
No comments yet