Description
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.
Affected products
opentelemetry: opentelemetry
References4
- github.com/open-telemetry/opentelemetry-dotnet/security/advisor… Vendor Advisory
- github.com/open-telemetry/opentelemetry-dotnet/pull/6564 Issue TrackingPatch
- github.com/open-telemetry/opentelemetry-dotnet/pull/7017 Issue TrackingPatch
- github.com/open-telemetry/opentelemetry-proto/pull/781 Issue Tracking
Metrics
- CVSS 3.1
-
5.9
MEDIUM
Score source: NVD
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H - EPSS — exploit probability
- 0% percentile: 24 · as of 13 November 2026
- CWE
- CWE-789
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.