CVE-2026-81870: open-telemetry opentelemetry-go · Information Exposure
Affects open-telemetry opentelemetry-goSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low : upgrade to 1.45.0 when convenient.
Data as of 31 Oct 2026, 20:20 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.45.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:NExploitation evidence
Disclosed: evidence found.
CVE published 16 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.
What to do
Upgrade opentelemetry-go and github.com/open-telemetry/opentelemetry-go to 1.45.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-telemetryopentelemetry-go | Affected
| Fixed in
|
Gogithub.com/open-telemetry/opentelemetry-gopkg:golang/github.com/open-telemetry/opentelemetry-goOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to opentelemetry-go version 1.45.0 or later where this issue is fixed. Alternatively, avoid enabling internal Info-level logging via otel.SetLogger to prevent exposure of sensitive configuration information. The default logging configuration does not emit the sensitive diagnostic event, so no action is required if default logging is used.
Description
OpenTelemetry-Go versions from 1.5.0 up to but not including 1.45.0 log detailed internal configuration information at the Info level when internal Info logging is enabled via otel.SetLogger. This can expose sensitive data such as OTLP collector endpoints, the OTLP HTTP Insecure flag, and full Zipkin collector URLs that may contain credentials or tokens. The default logger does not emit this event, and authentication headers, TLS keys, and span payloads are not logged. The issue is fixed in version 1.45.0.
References
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6v46-5gfg (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/pull/8438 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2ed42117ae541bb38 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/releases/tag/exporters/zipkin/v1.45.0 (opens in a new tab)
- github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/v1.45.0 (opens in a new tab)