CVE-2026-81870: OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs
OpenTelemetry Go versions 1.5.0 through 1.44.0 can include trace exporter endpoint configuration in an internal diagnostic log emitted when an SDK TracerProvider is created. The default OpenTelemetry logger does not emit this event. Exposure requires an application to install a logger that enables OpenTelemetry’s internal Info-level diagnostics and for someone other than the intended audience to have access to those logs.
The logged configuration can disclose the address of the trace collector and whether the OTLP/HTTP connection is configured as insecure. The Zipkin exporter logs its complete collector URL, so credentials in URL userinfo or tokens in the query string are also disclosed if an application embeds them there. OTLP authentication headers, TLS key material, and exported span data are not included in this log.
References
- github.com/advisories/GHSA-8wmf-6v46-5gfg
- github.com/open-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2ed42117ae541bb38
- github.com/open-telemetry/opentelemetry-go/pull/8438
- github.com/open-telemetry/opentelemetry-go/releases/tag/exporters/zipkin/v1.45.0
- github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/v1.45.0
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6v46-5gfg
- nvd.nist.gov/vuln/detail/CVE-2026-81870
Code Behaviors & Features
Detect and mitigate CVE-2026-81870 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →