CVE-2026-40182

5.3 MEDIUM
Published: April 23, 2026 Modified: April 29, 2026
View on NVD

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.

AI Explanation

Get an AI-powered plain-language explanation of this vulnerability and remediation steps.

Login to generate AI explanation

CVSS v3.x Details

0.0 Low Medium High Critical 10.0
Vector String
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

References to Advisories, Solutions, and Tools

Patch Vendor Advisory Exploit Third Party Advisory
https://github.com/open-telemetry/opentelemetry-dotnet/pull/6564
Source: security-advisories@github.com
Issue Tracking Patch
https://github.com/open-telemetry/opentelemetry-dotnet/pull/7017
Source: security-advisories@github.com
Issue Tracking Patch
https://github.com/open-telemetry/opentelemetry-proto/pull/781
Source: security-advisories@github.com
Issue Tracking

4 reference(s) from NVD

Quick Stats

CVSS v3 Score
5.3 / 10.0
EPSS (Exploit Probability)
0.0%
14th percentile
Exploitation Status
Not in CISA KEV

Weaknesses (CWE)

Affected Vendors

opentelemetry