Is go.opentelemetry.io/otel/sdk/log 0.7 vulnerable?

Go · 1 release from 0.7.0 to 0.7.0 · latest go.opentelemetry.io/otel/sdk/log is 1.47.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. go.opentelemetry.io/otel/sdk/log 0.7.0, the last 0.7 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2026-81872, CVE-2026-81872. Upgrade to 0.21.0 or later to fix all of them.

Upgrade with:go get go.opentelemetry.io/otel/sdk/log@v0.21.0

Is your project on an affected go.opentelemetry.io/otel/sdk/log?

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

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

Advisories affecting go.opentelemetry.io/otel/sdk/log 0.7.0

  • LowCVE-2026-81872GO-2026-66151 Oct 2026

    OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full in go.opentelemetry.io/otel/sdk/log

    Affected
    <0.21.0
    Fixed in
    0.21.0
  • MediumCVE-2026-81872GHSA-hjf4-fphr-2h6529 Sept 2026

    OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full

    Affected
    <0.21.0
    Fixed in
    0.21.0

Which of your client projects are still on go.opentelemetry.io/otel/sdk/log 0.7?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact go.opentelemetry.io/otel/sdk/log version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other go.opentelemetry.io/otel/sdk/log versions

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