CVE-2026-40182
OpenTelemetry dotnet is a dotnet telemetry framework. From 1.13.1 …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/open-telemetry/opentelemetry-dotnet/pull/6564
- github.com/open-telemetry/opentelemetry-dotnet/pull/7017
- github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-q834-8qmm-v933
- github.com/open-telemetry/opentelemetry-proto/pull/781
- nvd.nist.gov/vuln/detail/CVE-2026-40182
- github.com/advisories/GHSA-q834-8qmm-v933
- nvd.nist.gov/vuln/detail/CVE-2026-40182
- cve.org/CVERecord?id=CVE-2026-40182
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.