Is go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp 0.6 vulnerable?

Go · 1 release from 0.6.0 to 0.6.0 · latest go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp is 0.23.0 · checked 18 Nov 2026

Yes: 2 known advisories

Yes. go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp 0.6.0, the last 0.6 release, is affected by 2 known security advisories (1 medium, 1 low), including CVE-2026-39882, CVE-2026-39882. Upgrade to 0.19.0 or later to fix all of them.

Upgrade with:go get go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp@v0.19.0

Is your project on an affected go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp?

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/exporters/otlp/otlplog/otlploghttp 0.6.0

  • LowCVE-2026-39882GO-2026-498526 May 2026

    Oversized OTLP HTTP response bodies can cause memory exhaustion in go.opentelemetry.io/otel/exporters/otlp

    Affected
    <0.19.0
    Fixed in
    0.19.0
  • MediumCVE-2026-39882GHSA-w8rr-5gcm-pp588 Apr 2026

    opentelemetry-go: OTLP HTTP exporters read unbounded HTTP response bodies

    Affected
    <0.19.0
    Fixed in
    0.19.0

Which of your client projects are still on go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp 0.6?

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

Other go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp 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.