Advisory record · GHSA-8wmf-6v46-5gfg

OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs

CVSS 2.0 LowEPSS 0.0027 · 18th percentile

Published by the GitHub Advisory Database at 17 Sept 2026, 20:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
go.opentelemetry.io/otel/sdkGo>=1.5.0, <1.45.01.45.0
go.opentelemetry.io/otel/exporters/otlp/otlptraceGo>=1.5.0, <1.45.01.45.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpcGo>=1.5.0, <1.45.01.45.0
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttpGo>=1.5.0, <1.45.01.45.0
go.opentelemetry.io/otel/exporters/zipkinGo>=1.5.0, <1.45.01.45.0
Identifiers
GHSA-8wmf-6v46-5gfg · CVE-2026-81870 · GO-2026-6505
Weakness (CWE)
CWE-200 · CWE-532
Published
17 Sept 2026
Updated
1 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

OpenTelemetry Go modules sdk, otlptrace, otlptracegrpc, otlptracehttp and zipkin exporter, versions 1.5.0 through 1.44.0, log the trace exporter endpoint configuration at Info level when a TracerProvider is created. An attacker with access to those logs can learn the collector address and whether OTLP/HTTP is insecure, and any credentials or tokens embedded in a Zipkin collector URL. Exposure requires the application to enable verbose internal diagnostics. Upgrade to version 1.45.0 or later; until then, keep internal logging below Info verbosity and avoid putting credentials in endpoint URLs.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.0 Low 4.0 CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0027, the 18th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:12 UTC First seen by agentprime
  2. 31 Oct 2026, 14:12 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.