Is OpenTelemetry.Exporter.Jaeger 1.1 vulnerable?
NuGet · 1 release from 1.1.0 to 1.1.0 · latest OpenTelemetry.Exporter.Jaeger is 1.5.1 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. OpenTelemetry.Exporter.Jaeger 1.1.0, the last 1.1 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?
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.1.0
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
Which of your client projects are still on OpenTelemetry.Exporter.Jaeger 1.1?
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.