Bug 2535725 (CVE-2026-81871) - CVE-2026-81871 go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: OpenTelemetry-Go: TLS certificate bypass allows log telemetry interception and alteration
Summary: CVE-2026-81871 go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: O...
Keywords:
Status: NEW
Alias: CVE-2026-81871
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2536929 2536930 2536931 2536933 2536934 2536935 2536936 2536937 2536938
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-09-16 21:13 UTC by OSIDB Bzimport
Modified: 2026-09-18 09:44 UTC (History)
74 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-09-16 21:13:26 UTC
OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the exporters/otlp/otlplog/otlploggrpc package loads OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE, OTEL_EXPORTER_OTLP_CERTIFICATE, and related client certificate environment variables through loadEnvTLS into cfg.tlsCfg, but newGRPCDialOptions does not apply cfg.tlsCfg when creating gRPC transport credentials. The environment-only TLS path instead uses credentials.NewTLS with system roots and no configured client certificate, bypassing intended private CA pinning and mutual TLS unless the application also supplies WithTLSCredentials. A network attacker able to intercept or spoof the collector connection with a system-trusted certificate can read or alter log telemetry. This issue is fixed in version 0.21.0.


Note You need to log in before you can comment on or make changes to this bug.