CVE-2026-40182: OpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies
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.
References
- github.com/advisories/GHSA-q834-8qmm-v933
- 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
Code Behaviors & Features
Detect and mitigate CVE-2026-40182 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →