# CVE-2026-41484: OpenTelemetry.Exporter.OneCollector vulnerable to denial of service via unbounded HTTP error response body

> An attacker controlling the telemetry endpoint can cause a denial of service by sending large HTTP error responses, leading to memory exhaustion in applications using the OpenTelemetry OneCollector exporter.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-55m9-299j-53c7

## What is CVE-2026-41484?

CVE-2026-41484 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet-contrib, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

## Which versions are affected by CVE-2026-41484?

2 open source packages ship an affected version, including OpenTelemetry.Exporter.OneCollector. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `OpenTelemetry.Exporter.OneCollector` | NuGet | All versions | 1.15.1 |
| `OpenTelemetry.Exporter.OneCollector` | NuGet | All versions | 1.15.1 |

Products: Opentelemetry Opentelemetry.exporter.onecollector.

## How do I fix CVE-2026-41484?

Upgrade OpenTelemetry.Exporter.OneCollector to 1.15.1 or later.

## Is CVE-2026-41484 being exploited?

There is no known exploitation of CVE-2026-41484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41484 and fix it if it is affected.

What it is: CVE-2026-41484 is a medium-severity denial of service vulnerability in open-telemetry opentelemetry-dotnet-contrib, published on 6 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-41484 in the wild and no public exploit code.

Affected packages and fixed versions:
- OpenTelemetry.Exporter.OneCollector (NuGet): affected all versions; fixed in 1.15.1
- OpenTelemetry.Exporter.OneCollector (NuGet): affected all versions; fixed in 1.15.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41484/ (Markdown: https://insights.sbomify.com/CVE-2026-41484/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41484
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41484
- OSV: https://osv.dev/vulnerability/CVE-2026-41484

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41484/
Summaries are generated and may contain mistakes; the official description above is the record.