CVE-2026-41484: OpenTelemetry.Exporter.OneCollector OneCollector Exporter Reads Unbounded HTTP Vulnerability

MODERATE
Advisory Identifier: GHSA-55m9-299j-53c7
CVSS 5.3
CWE-770
Published
Advisory Summary

CVE-2026-41484 is a MODERATE (CVSS 5.3) onecollector exporter reads unbounded http vulnerability (CWE-770: Allocation of Resources Without Limits or Throttling) affecting OpenTelemetry.Exporter.OneCollector libraries in the NuGet ecosystem. The issue involves onecollector exporter reads unbounded http response bodies. Remediation is available by upgrading affected packages to version 1.15.1.

CVE-2026-41484 at a Glance

CVE Identifier CVE-2026-41484
GHSA Identifier GHSA-55m9-299j-53c7
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-770: Allocation of Resources Without Limits or Throttling
Affected Product OpenTelemetry.Exporter.OneCollector
Package Ecosystem NuGet
Published Date
Last Updated

Security Impact

CVSS: 5.3

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H).

Attack Vector Adjacent (AV:A)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity None (I:N)
Availability High (A:H)

How to Fix CVE-2026-41484

To remediate this vulnerability, upgrade all affected OpenTelemetry.Exporter.OneCollector dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

OpenTelemetry.Exporter.OneCollector fixed: 1.15.1
Upgrade OpenTelemetry.Exporter.OneCollector to 1.15.1
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for OpenTelemetry.Exporter.OneCollector

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-41484, inspect your project dependencies for OpenTelemetry.Exporter.OneCollector:

inspect dependencies for OpenTelemetry.Exporter.OneCollector

Analyze the terminal output to locate any version of OpenTelemetry.Exporter.OneCollector in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-770: Allocation of Resources Without Limits or Throttling, where the product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated. In OpenTelemetry.Exporter.OneCollector, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Details The [`HttpJsonPostTransport`](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/171c6b81f88831641b56b470e6f92862e605013d/src/OpenTelemetry.Exporter.OneCollector/Internal/Transports/HttpJsonPostTransport.cs) class reads the response body when a non-200 HTTP status code is received when exporting telemetry to aid debugging by operators so that the error response is included in the logs emitted by the exporter. An attacker who controls the configured endpoint, or who can intercept traffic to them (MiTM), 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. ### Impact If an application using the OneCollector exporter is configured to use a back-end/collector endpoint that is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response the application could have its memory exhausted and create a denial-of-service condition. ### Mitigation The application's configured back-end/collector endpoint needs to behave maliciously. If the collector/back-end is a well-behaved implementation response bodies should not be excessively large if a request error occurs. ### Workarounds Use network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint. ### Remediation [#4117](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117) updates the OneCollector exporter to limit the number of bytes read from the response body in an error condition to 4MiB. ### Resources - [#4117](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117)

CVE-2026-41484 Affected OpenTelemetry.Exporter.OneCollector Versions

1 component(s)
Fixed Versions:
1.15.1
Product / Package Ecosystem Affected Versions Fixed Version
OpenTelemetry.Exporter.OneCollector
NuGet
< 1.15.1
1.15.1

References

Frequently Asked Questions

What is CVE-2026-41484?
CVE-2026-41484 is a security vulnerability in OpenTelemetry.Exporter.OneCollector involving OneCollector exporter reads unbounded HTTP response bodies under CWE-770: Allocation of Resources Without Limits or Throttling.
Which OpenTelemetry.Exporter.OneCollector versions are affected?
Affected versions include releases prior to 1.15.1 across affected packages: OpenTelemetry.Exporter.OneCollector.
What version fixes CVE-2026-41484?
Upgrading to 1.15.1 (or the latest patched release for your respective branch) resolves the vulnerability.
Is OpenTelemetry.Exporter.OneCollector affected?
Yes, OpenTelemetry.Exporter.OneCollector is affected in releases prior to 1.15.1. Upgrade your dependency to 1.15.1 or later.
What is the CVSS score of CVE-2026-41484?
CVE-2026-41484 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H.
What CWE is associated with CVE-2026-41484?
CVE-2026-41484 is classified under CWE-770: Allocation of Resources Without Limits or Throttling (The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.).
How can I check NuGet dependencies for CVE-2026-41484?
Run the dependency tree command: 'inspect dependencies for OpenTelemetry.Exporter.OneCollector'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-55m9-299j-53c7",
  "modified" : "2026-05-08T19:32:50Z",
  "published" : "2026-04-29T20:17:57Z",
  "aliases" : [ "CVE-2026-41484" ],
  "summary" : "OneCollector exporter reads unbounded HTTP response bodies",
  "details" : "### Summary\n\nWhen 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.\n\nThis 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.\n\n### Details\n\nThe [`HttpJsonPostTransport`](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/blob/171c6b81f88831641b56b470e6f92862e605013d/src/OpenTelemetry.Exporter.OneCollector/Internal/Transports/HttpJsonPostTransport.cs) class reads the response body when a non-200 HTTP status code is received when exporting telemetry to aid debugging by operators so that the error response is included in the logs emitted by the exporter.\n\nAn attacker who controls the configured endpoint, or who can intercept traffic to them (MiTM), 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.\n\n### Impact\n\nIf an application using the OneCollector exporter is configured to use a back-end/collector endpoint that is attacker-controlled (or a network attacker can MitM the connection) and an extremely large body is returned by the response the application could have its memory exhausted and create a denial-of-service condition.\n\n### Mitigation\n\nThe application's configured back-end/collector endpoint needs to behave maliciously. If the collector/back-end is a well-behaved implementation response bodies should not be excessively large if a request error occurs.\n\n### Workarounds\n\nUse network-level controls (firewall rules, mTLS, service mesh) to prevent Man-in-the-Middle (MitM) attacks on the configured back-end/collector endpoint.\n\n### Remediation\n\n[#4117](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117) updates the OneCollector exporter to limit the number of bytes read from the response body in an error condition to 4MiB.\n\n### Resources\n\n- [#4117](https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117)",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "OpenTelemetry.Exporter.OneCollector"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.15.1"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 1.15.0"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet-contrib/security/advisories/GHSA-55m9-299j-53c7"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-41484"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet-contrib/pull/4117"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet-contrib/commit/77dc5d14fcdf6c6b3aeba5f8bba5dfded90495c9"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet-contrib"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-770" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-29T20:17:57Z",
    "nvd_published_at" : "2026-05-06T22:16:26Z"
  }
}