LowGO-2026-6505CVE-2026-81870GHSA-8wmf-6v46-5gfg

OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs in go.opentelemetry.io/otel/exporters/otlp/otlptrace

Published 1 Oct 2026 · Updated 1 Oct 2026

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

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

Affected packages

Affected
>=1.5.0 <1.45.0
Fixed in
1.45.0
Update to the fixed version for your release line, for example:go get go.opentelemetry.io/otel/exporters/otlp/otlptrace@v1.45.0
Affected
>=1.5.0 <1.45.0
Fixed in
1.45.0
Update to the fixed version for your release line, for example:go get go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc@v1.45.0
Affected
>=1.5.0 <1.45.0
Fixed in
1.45.0
Update to the fixed version for your release line, for example:go get go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.45.0
Affected
>=1.5.0 <1.45.0
Fixed in
1.45.0
Update to the fixed version for your release line, for example:go get go.opentelemetry.io/otel/exporters/zipkin@v1.45.0
Affected
>=1.5.0 <1.45.0
Fixed in
1.45.0
Update to the fixed version for your release line, for example:go get go.opentelemetry.io/otel/sdk@v1.45.0

Details

OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs in go.opentelemetry.io/otel/exporters/otlp/otlptrace

Is GO-2026-6505 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected go.opentelemetry.io/otel/exporters/otlp/otlptrace, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.