Low, CVSS 2.0GoAmendedPublished
OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs
CVE-2026-81870 · GHSA-8wmf-6v46-5gfg
- Affected
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace >= 1.5.0, <= 1.44.0
- Fixed in
- 1.45.0· Vendor fix available
- Issue
- 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. Exporter MarshalLog implementations that caused this configuration to be included in internal logs were introduced by a1fff3c. Details When…
Recommended action: Upgrade to 1.45.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.