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.
References
| Link | Resource |
|---|---|
| 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 |
Configurations
History
No history.
Information
Published : 2026-04-23 18:16
Updated : 2026-06-17 10:44
NVD link : CVE-2026-40182
Mitre link : CVE-2026-40182
CVE.ORG link : CVE-2026-40182
JSON object : View
Products Affected
opentelemetry
- opentelemetry
CWE
CWE-789
Memory Allocation with Excessive Size Value
