Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Opentelemetry | Opentelemetry | >= 1.13.1, < 1.15.2 |
Related Weaknesses (CWE)
References
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/6564Issue TrackingPatch
- https://github.com/open-telemetry/opentelemetry-dotnet/pull/7017Issue TrackingPatch
- https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-Vendor Advisory
- https://github.com/open-telemetry/opentelemetry-proto/pull/781Issue Tracking
FAQ
What is CVE-2026-40182?
CVE-2026-40182 is a vulnerability with a CVSS score of 5.3 (MEDIUM). 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 th...
How severe is CVE-2026-40182?
CVE-2026-40182 has been rated MEDIUM with a CVSS base score of 5.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-40182?
Check the references section above for vendor advisories and patch information. Affected products include: Opentelemetry Opentelemetry.