Back to CVE records
Medium 5.3Published Apr 23, 2026

CVE-2026-40182OpenTelemetry dotnet: OTLP exporter reads unbounded HTTP response bodies

Updated under an hour ago ()

Does this affect you?

It affects open-telemetry opentelemetry-dotnet and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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
5.3 MEDIUM (v3.1, CNA)CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-789
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Apr 23, 2026
First seen by InfoSec Signals
Oct 9, 2026

Affected products

Affected products
open-telemetry opentelemetry-dotnet
open_telemetry:opentelemetry_dotnet (from the name)
from 1.13.1, < 1.15.2
CNA record
opentelemetry opentelemetry
opentelemetry:opentelemetry
from 1.13.1 before 1.15.2
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.