CVE-2026-41484: OneCollector exporter reads unbounded HTTP response bodies
(updated )
When exporting telemetry to a back-end/collector over HTTP using the OpenTelemetry.Exporter.OneCollector exporter, 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-55m9-299j-53c7
- github.com/open-telemetry/opentelemetry-dotnet-contrib
- github.com/open-telemetry/opentelemetry-dotnet-contrib/commit/77dc5d14fcdf6c6b3aeba5f8bba5dfded90495c9
- github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117
- github.com/open-telemetry/opentelemetry-dotnet-contrib/security/advisories/GHSA-55m9-299j-53c7
- nvd.nist.gov/vuln/detail/CVE-2026-41484
Code Behaviors & Features
Detect and mitigate CVE-2026-41484 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →