Is OpenTelemetry.Instrumentation.AspNetCore 1.8 vulnerable?

NuGet · 2 releases from 1.8.0 to 1.8.1 · latest OpenTelemetry.Instrumentation.AspNetCore is 1.21.0 · checked 18 Nov 2026

No known advisories in the last release

OpenTelemetry.Instrumentation.AspNetCore 1.8.1, the last 1.8 release, has no known advisories. 1 advisory affects earlier 1.8.x releases, so update to 1.8.1.

Update within 1.8:dotnet add package OpenTelemetry.Instrumentation.AspNetCore --version 1.8.1

Is your project on an affected OpenTelemetry.Instrumentation.AspNetCore?

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

Fixed within 1.8.x, affecting earlier releases

  • MediumCVE-2024-32028GHSA-vh2m-22xx-q94f12 Apr 2024

    Sensitive query parameters logged by default in OpenTelemetry.Instrumentation http and AspNetCore

    Affected
    <1.8.1
    Fixed in
    1.8.1

Every OpenTelemetry.Instrumentation.AspNetCore 1.8.x release

Affected: 1.8.0. 1.8.1 is not affected. Latest OpenTelemetry.Instrumentation.AspNetCore: 1.21.0.

VersionKnown advisories
OpenTelemetry.Instrumentation.AspNetCore 1.8.1None
OpenTelemetry.Instrumentation.AspNetCore 1.8.0CVE-2024-32028

Which of your client projects are still on OpenTelemetry.Instrumentation.AspNetCore 1.8?

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

Other OpenTelemetry.Instrumentation.AspNetCore 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.