CVE-2026-81870: OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs
OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
OpenTelemetry-Goto a version that resolves this vulnerability.Fixed in 1.45.0
Event History
Frequently Asked Questions
Which deployments are exposed to this logging leak?
Deployments using OpenTelemetry-Go versions 1.5.0 through 1.44.0 are exposed only if they call otel.SetLogger and enable OpenTelemetry internal Info-level logging. The default OpenTelemetry logger does not emit the affected event.
What information could an observer recover from affected logs?
Affected logs can reveal OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure setting, and complete Zipkin collector URLs. Zipkin URLs may expose credentials or tokens if those are embedded in URL user information or query strings.
What should teams do if they cannot immediately upgrade?
Disable OpenTelemetry internal Info-level logging or avoid configuring it through otel.SetLogger, and restrict access to existing application logs. Review logs produced when TracerProvider instances were created for Zipkin URLs containing user information or query-string credentials or tokens.
What information is not included by this logging path?
The affected event does not log OTLP authentication headers, TLS key material, or span payloads.