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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.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 · score source

EPSS

• CVE-2026-81870: 0.27% estimated exploitation activity in the next 30 days; percentile 18.58 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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…

Published by the source

17 Sep 2026, 20:31 UTC

Last modified by the source

1 Oct 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:29 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-8wmf-6v46-5gfg

2. Revision 3 · amended · 25 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6505

4. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-8wmf-6v46-5gfg

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-81870

Advisory: OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs
IDs: CVE-2026-81870, GHSA-8wmf-6v46-5gfg
Record: https://patchnext.com/advisories/cve-2026-81870 (revision 4, source checked 26 Oct 2026, 15:29 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc 1.45.0; go.opentelemetry.io/otel/exporters/otlp/otlptrace 1.45.0; go.opentelemetry.io/otel/sdk 1.45.0; go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp 1.45.0; go.opentelemetry.io/otel/exporters/zipkin 1.45.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc: affected >= 1.5.0, <= 1.44.0; fixed in 1.45.0
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace: affected >= 1.5.0, <= 1.44.0; fixed in 1.45.0
- Go go.opentelemetry.io/otel/sdk: affected >= 1.5.0, <= 1.44.0; fixed in 1.45.0
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp: affected >= 1.5.0, <= 1.44.0; fixed in 1.45.0
- Go go.opentelemetry.io/otel/exporters/zipkin: affected >= 1.5.0, <= 1.44.0; fixed in 1.45.0

## Suggested inspection (read-only)
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/sdk: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/exporters/zipkin: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc, go.opentelemetry.io/otel/exporters/otlp/otlptrace, go.opentelemetry.io/otel/sdk, go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp, go.opentelemetry.io/otel/exporters/zipkin.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-8wmf-6v46-5gfg (OSV record GHSA-8wmf-6v46-5gfg lists affected ranges: Go go.opentelemetry.io/otel/sdk >=1.5.0 =1.5.0 =1.5.0 =1.5.0 =1.5.0 <1.45.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6505 (OSV record GO-2026-6505 lists affected ranges: Go go.opentelemetry.io/otel/exporters/otlp/otlptrace >=1.5.0 =1.5.0 =1.5.0 =1.5.0 =1.5.0 <1.45.0 (fixed))
- Verified: https://github.com/advisories/GHSA-8wmf-6v46-5gfg (GitHub-reviewed advisory GHSA-8wmf-6v46-5gfg lists affected ranges: Go go.opentelemetry.io/otel/sdk >=1.5.0 =1.5.0 =1.5.0 =1.5.0 =1.5.0 <=1.44.0)

Commands are suggestions: review each one before running it.