OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 to before 1.15.2, When exporting telemetry to a back-end/collector over gRPC or HTTP using OpenTelemetry Protocol format (OTLP), if the request results in a unsuccessful request (i.e. HTTP 4xx or 5xx), the response is read into memory with no upper-bound on the number of bytes consumed. This could cause memory exhaustion in the consuming application if the configured back-end/collector endpoint is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response. This vulnerability is fixed in 1.15.2.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/6564 Issue Tracking, Patch
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/7017 Issue Tracking, Patch
- https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 5.9 · opentelemetryNVD modified 2026-10-26 22:10
Affected (CPE criteria) 1
cpe:2.3:a:opentelemetry:opentelemetry:*:*:*:*:*:.net:*:*
References 4
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/6564 Issue Tracking, Patch
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/7017 Issue Tracking, Patch
- https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933 Vendor Advisory
- https://github.com/open-telemetry/opentelemetry-proto/pull/781 Issue Tracking