CVE Catalog

CVE-2026-41484

MediumCVSS 5.3
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Low risk
0.34%

27th percentile - higher than 27% of all known CVEs

Summary

In OpenTelemetry.Exporter.OneCollector versions 1.15.0 and earlier, when a request to the configured back-end or collector results in an unsuccessful HTTP 4xx or 5xx response, the HttpJsonPostTransport class reads the entire response body into memory with no upper bound on bytes consumed. An attacker who controls the endpoint or performs a man-in-the-middle attack can return an arbitrarily large response body, causing unbounded heap allocation, memory pressure, GC stalls, or an OutOfMemoryException that terminates the process.

Risk Assessment

An attacker can remotely cause memory exhaustion and termination of the application process, leading to denial of service. This affects the availability of telemetry systems and applications using the exporter.

Recommendation

Upgrade OpenTelemetry.Exporter.OneCollector to version 1.15.1. As a workaround, use network-level controls such as firewall rules, mTLS, or a service mesh to prevent man-in-the-middle attacks.

Related vulnerabilities

Original NVD description (English source)

OpenTelemetry.Exporter.OneCollector is a .NET exporter that sends telemetry to a OneCollector back-end over HTTP. In versions 1.15.0 and earlier, when a request to the configured back-end or collector results in an unsuccessful HTTP 4xx or 5xx response, the HttpJsonPostTransport class reads the entire response body into memory with no upper bound on the number of bytes consumed in order to include the error response in operator logs. An attacker who controls the configured endpoint, or who can intercept traffic to it via a man-in-the-middle attack, can return an arbitrarily large response body. This causes unbounded heap allocation in the consuming process, leading to high transient memory pressure, garbage-collection stalls, or an OutOfMemoryException that terminates the process. As a workaround, use network-level controls such as firewall rules, mTLS, or a service mesh to prevent man-in-the-middle attacks on the configured back-end or collector endpoint. This issue is fixed in version 1.15.1, which limits the number of bytes read from the response body in an error condition to 4 MiB.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS