Is OpenTelemetry.AutoInstrumentation 1.10 vulnerable?

NuGet · 1 release from 1.10.0 to 1.10.0 · latest OpenTelemetry.AutoInstrumentation is 1.19.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. OpenTelemetry.AutoInstrumentation 1.10.0, the last 1.10 release, is affected by 1 known security advisory (1 high). Upgrade to 1.11.0 or later to fix all of them.

Upgrade with:dotnet add package OpenTelemetry.AutoInstrumentation --version 1.11.0

Is your project on an affected OpenTelemetry.AutoInstrumentation?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting OpenTelemetry.AutoInstrumentation 1.10.0

  • HighGHSA-vc29-vg52-66436 Mar 2025

    DoS Vulnerability in TraceContextPropagator.Extract - OpenTelemetry.Api

    Affected
    >=1.10.0-beta.1 <1.11.0
    Fixed in
    1.11.0

Which of your client projects are still on OpenTelemetry.AutoInstrumentation 1.10?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact OpenTelemetry.AutoInstrumentation version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other OpenTelemetry.AutoInstrumentation versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.