Vulnerabilities in pkg:nuget/OpenTelemetry.Api

PACKAGE
Advisory Identifier: GHSA-g94r-2vxg-569j
Advisory Summary

CVE-2026-40894 is a MODERATE (CVSS 5.3) excessive memory allocation when parsing vulnerability (CWE-789: Memory Allocation with Excessive Size Value) affecting OpenTelemetry dotnet libraries in the NuGet ecosystem. The issue involves excessive memory allocation when parsing opentelemetry propagation headers. Remediation is available by upgrading affected packages to version 1.15.3.

2 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:nuget/OpenTelemetry.Api

2 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:nuget/OpenTelemetry.Api. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-g94r-2vxg-569j CVE-2026-40894 MODERATE OpenTelemetry dotnet: Excessive memory allocation when parsing OpenTelemetry propagation headers
GHSA-8785-wc3w-h8q6 CVE-2025-27513 MODERATE OpenTelemetry .NET has Denial of Service (DoS) Vulnerability in API Package

CVE-2026-40894 at a Glance

CVE Identifier CVE-2026-40894
GHSA Identifier GHSA-g94r-2vxg-569j
Severity MODERATE
CVSS v3.1 Base Score 5.3
CWE Classification CWE-789: Memory Allocation with Excessive Size Value
Affected Product OpenTelemetry dotnet
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:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L).

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

How to Fix CVE-2026-40894

To remediate this vulnerability, upgrade all affected OpenTelemetry dotnet 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.Api fixed: 1.15.3
Upgrade OpenTelemetry.Api to 1.15.3
OpenTelemetry.Extensions.Propagators fixed: 1.15.3
Upgrade OpenTelemetry.Extensions.Propagators to 1.15.3
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.Api

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-40894, inspect your project dependencies for OpenTelemetry dotnet:

inspect dependencies for OpenTelemetry.Api

Analyze the terminal output to locate any version of OpenTelemetry dotnet in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.15.3), 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-789: Memory Allocation with Excessive Size Value, where the product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. In OpenTelemetry dotnet, 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 The implementation details of the baggage, B3 and Jaeger processing code in the `OpenTelemetry.Api` and `OpenTelemetry.Extensions.Propagators` NuGet packages can allocate excessive memory when parsing which could create a potential denial of service (DoS) in the consuming application. ### Details #### Exceeding Limits [`BaggagePropagator.Inject<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/fc1a2864d1665bda857089e11fe9247e3c75637a/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L93-L112) does not enforce the length limit of `8192` characters if the injected baggage contains only one item. This change was introduced by #1048. #### Excessive allocation The following methods eagerly allocate intermediate arrays before applying size limits. - [`BaggagePropagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L52-L55) - this change was introduced by #1048. - [`BaggagePropagator.Inject<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L138-L157) - this change was introduced by #1048. - [`B3Propagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Extensions.Propagators/B3Propagator.cs#L203-L207) - this change was introduced by #533. - [`B3Propagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/B3Propagator.cs#L204-L214) - this change was introduced by #3244. - [`JaegerPropagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Extensions.Propagators/JaegerPropagator.cs#L150-L154) - this change was introduced by #3309. ### Impact Excessively large propagation headers, particularly in degenerate/malformed cases that consist or large numbers of delimiter characters, can allocate excessive amounts of memory for intermediate storage of parsed content relative to the size of the original input. ### Mitigation HTTP servers often set maximum limits on the length of HTTP request headers, such as [Internet Information Services (IIS)](https://learn.microsoft.com/iis/configuration/system.webserver/security/requestfiltering/requestlimits/headerlimits/) which sets a default limit of 16KB and [nginx](https://nginx.org/docs/http/ngx_http_core_module.html#large_client_header_buffers) which sets a default limit of 8KB. ### Workarounds Possible workarounds include: - Configuring appropriate HTTP request header limits. - Disabling baggage and/or trace propagation. ### Remediation [#7061](https://github.com/open-telemetry/opentelemetry-dotnet/pull/7061) refactors the handling of baggage, B3 and Jaeger propagation headers to stop parsing eagerly when limits are exceeded and avoid allocating intermediate arrays.

CVE-2026-40894 Affected OpenTelemetry dotnet Versions

2 component(s)
Fixed Versions:
1.15.3
Product / Package Ecosystem Affected Versions Fixed Version
OpenTelemetry.Api
NuGet
≥ 0.5.0-beta.2
< 1.15.3
1.15.3
OpenTelemetry.Extensions.Propagators
NuGet
≥ 1.3.1
< 1.15.3
1.15.3

References

Frequently Asked Questions

What is CVE-2026-40894?
CVE-2026-40894 is a security vulnerability in OpenTelemetry dotnet involving Excessive memory allocation when parsing OpenTelemetry propagation headers under CWE-789: Memory Allocation with Excessive Size Value.
Which OpenTelemetry dotnet versions are affected?
Affected versions include releases prior to 1.15.3 across affected packages: OpenTelemetry.Api, OpenTelemetry.Extensions.Propagators.
What version fixes CVE-2026-40894?
Upgrading to 1.15.3 (or the latest patched release for your respective branch) resolves the vulnerability.
Is OpenTelemetry.Api affected?
Yes, OpenTelemetry.Api is affected in releases prior to 1.15.3. Upgrade your dependency to 1.15.3 or later.
Is OpenTelemetry.Extensions.Propagators affected?
Yes, OpenTelemetry.Extensions.Propagators is affected in releases prior to 1.15.3. Upgrade your dependency to 1.15.3 or later.
What is the CVSS score of CVE-2026-40894?
CVE-2026-40894 has a CVSS v3.1 base score of 5.3 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L.
What CWE is associated with CVE-2026-40894?
CVE-2026-40894 is classified under CWE-789: Memory Allocation with Excessive Size Value (The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.).
How can I check NuGet dependencies for CVE-2026-40894?
Run the dependency tree command: 'inspect dependencies for OpenTelemetry.Api'. 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-g94r-2vxg-569j",
  "modified" : "2026-04-23T21:43:54Z",
  "published" : "2026-04-23T21:43:53Z",
  "aliases" : [ "CVE-2026-40894" ],
  "summary" : "OpenTelemetry dotnet: Excessive memory allocation when parsing OpenTelemetry propagation headers",
  "details" : "### Summary\n\nThe implementation details of the baggage, B3 and Jaeger processing code in the `OpenTelemetry.Api` and `OpenTelemetry.Extensions.Propagators` NuGet packages can allocate excessive memory when parsing which could create a potential denial of service (DoS) in the consuming application.\n\n### Details\n\n#### Exceeding Limits\n\n[`BaggagePropagator.Inject<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/fc1a2864d1665bda857089e11fe9247e3c75637a/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L93-L112) does not enforce the length limit of `8192` characters if the injected baggage contains only one item.\n\nThis change was introduced by #1048.\n\n#### Excessive allocation\n\nThe following methods eagerly allocate intermediate arrays before applying size limits.\n\n- [`BaggagePropagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L52-L55) - this change was introduced by #1048.\n- [`BaggagePropagator.Inject<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/BaggagePropagator.cs#L138-L157) - this change was introduced by #1048.\n- [`B3Propagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Extensions.Propagators/B3Propagator.cs#L203-L207) - this change was introduced by #533.\n- [`B3Propagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Api/Context/Propagation/B3Propagator.cs#L204-L214) - this change was introduced by #3244.\n- [`JaegerPropagator.Extract<T>()`](https://github.com/open-telemetry/opentelemetry-dotnet/blob/888d1bf2489fb7408d3c5e8758a5bbffa89a8fb2/src/OpenTelemetry.Extensions.Propagators/JaegerPropagator.cs#L150-L154) - this change was introduced by #3309.\n\n### Impact\n\nExcessively large propagation headers, particularly in degenerate/malformed cases that consist or large numbers of delimiter characters, can allocate excessive amounts of memory for intermediate storage of parsed content relative to the size of the original input.\n\n### Mitigation\n\nHTTP servers often set maximum limits on the length of HTTP request headers, such as [Internet Information Services (IIS)](https://learn.microsoft.com/iis/configuration/system.webserver/security/requestfiltering/requestlimits/headerlimits/) which sets a default limit of 16KB and [nginx](https://nginx.org/docs/http/ngx_http_core_module.html#large_client_header_buffers) which sets a default limit of 8KB.\n\n### Workarounds\n\nPossible workarounds include:\n\n- Configuring appropriate HTTP request header limits.\n- Disabling baggage and/or trace propagation.\n\n### Remediation\n\n[#7061](https://github.com/open-telemetry/opentelemetry-dotnet/pull/7061) refactors the handling of baggage, B3 and Jaeger propagation headers to stop parsing eagerly when limits are exceeded and avoid allocating intermediate arrays.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "OpenTelemetry.Api"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0.5.0-beta.2"
      }, {
        "fixed" : "1.15.3"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "NuGet",
      "name" : "OpenTelemetry.Extensions.Propagators"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "1.3.1"
      }, {
        "fixed" : "1.15.3"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/security/advisories/GHSA-g94r-2vxg-569j"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-40894"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/1048"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/3244"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/3309"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/3533"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/533"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/pull/7061"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/open-telemetry/opentelemetry-dotnet/releases/tag/core-1.15.3"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-789" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-04-23T21:43:53Z",
    "nvd_published_at" : "2026-04-23T19:17:28Z"
  }
}