Is OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11 vulnerable?

NuGet · 3 releases from 1.11.0 to 1.11.2 · latest OpenTelemetry.Exporter.OpenTelemetryProtocol is 1.21.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.2, the last 1.11 release, is affected by 1 known security advisory (1 medium), including CVE-2026-42191. Upgrade to 1.15.3 or later to fix all of them.

Upgrade with:dotnet add package OpenTelemetry.Exporter.OpenTelemetryProtocol --version 1.15.3

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

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.OpenTelemetryProtocol 1.11.2

  • MediumCVE-2026-42191GHSA-4625-4j76-fww930 Apr 2026

    OpenTelemetry's disk retry default temp path enables local blob injection via OTLP Exporter

    Affected
    >=1.8.0 <1.15.3
    Fixed in
    1.15.3

Every OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.x release

Affected: 1.11.0 to 1.11.2. Latest OpenTelemetry.Exporter.OpenTelemetryProtocol: 1.21.0.

VersionKnown advisories
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.2CVE-2026-42191
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.1CVE-2026-42191
OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11.0CVE-2026-42191

Which of your client projects are still on OpenTelemetry.Exporter.OpenTelemetryProtocol 1.11?

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

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