Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

NuGet package

opentelemetry.extensions.propagators

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 5.3NuGetPublished

    OpenTelemetry dotnet: Excessive memory allocation when parsing OpenTelemetry propagation headers

    CVE-2026-40894 · GHSA-g94r-2vxg-569j

    Affected
    • NuGet opentelemetry.extensions.propagators >= 1.3.1, < 1.15.3
    Fixed in
    1.15.3· Vendor fix available
    Issue
    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() 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() - this change was introduced by #1048. - BaggagePropagator.Inject<T() - this change was introduced by #1048. - B3Propagator.Extract<T() - this change was introduced by #533. - B3Propagator.Extract<T() - this change was introduced by #3244. - JaegerPropagator.Extract<T() - this change was introduced by #3309. Impact Excessively large propagation headers, particularly in…

    Recommended action: Upgrade to 1.15.3 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →