Is OpenTelemetry.Exporter.Jaeger 1.5 vulnerable?

NuGet · 2 releases from 1.5.0 to 1.5.1 · latest OpenTelemetry.Exporter.Jaeger is 1.5.1 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. OpenTelemetry.Exporter.Jaeger 1.5.1, the last 1.5 release, is affected by 1 known security advisory (1 medium), including CVE-2026-41078. At least one has no fixed release yet.

Is your project on an affected OpenTelemetry.Exporter.Jaeger?

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.Exporter.Jaeger 1.5.1

  • MediumCVE-2026-41078GHSA-38h3-2333-qx4718 Apr 2026

    OpenTelemetry .NET has potential memory exhaustion via unbounded pooled-list sizing in Jaeger exporter conversion path

    Affected
    <=1.6.0-rc.1
    Fixed in
    No fix released

Every OpenTelemetry.Exporter.Jaeger 1.5.x release

Affected: 1.5.0 to 1.5.1.

VersionKnown advisories
OpenTelemetry.Exporter.Jaeger 1.5.1CVE-2026-41078
OpenTelemetry.Exporter.Jaeger 1.5.0CVE-2026-41078

Which of your client projects are still on OpenTelemetry.Exporter.Jaeger 1.5?

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

Other OpenTelemetry.Exporter.Jaeger 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.