Search threats, CVEs… ⌘K
← Back to CVE intelligence
CVE intelligence

CVE-2026-81870

Vulnerability intelligence

Published Sep 16, 2026Sources checked Nov 11, 2026
2.0LOWCVSS out of 10
What this means

Review the available evidence

CVE-2026-81870 and is rated Low severity with a CVSS score of 2.0. It is not in the current CISA KEV record we collected. That does not prove exploitation has not occurred.

What to do next

Remediation and response

Microsoft Security Response Center guidance

Vendor revision: Nov 2, 2026
Vendor remediation details

Release Notes

Vendor-listed releases

  • 3.5.35-1
  • 1.7.0-2
  • 2.27.0-16
  • 0.24.2-34
  • 3.15.0.aks0-23
  • 1.12.15-15
  • 2.4.0-1
  • 0.14.0-19
  • 4.1.0.kata1-2
  • 0.0.10-11
  • 1.7.7-19
  • 2.3.7-1
CISA KEVNot listedBased on the latest collected catalog
EPSS0.3%Estimated 30-day exploitation probability
Ransomware useNot markedCISA KEV ransomware field
Threat actors0Source-linked actor relationships
Overview

What is CVE-2026-81870?

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.

Source: NVD