Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The OTLP log gRPC exporter in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc, versions before 0.21.0, loads TLS certificate settings from environment variables but does not apply them to the connection, so CA pinning and client certificates configured that way are ignored. An attacker who can intercept or spoof the collector connection using a certificate trusted by the system can read or alter log data. Upgrade to 0.21.0 or later; without upgrading, pass the TLS settings explicitly with WithTLSCredentials.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 6.3 | Medium | 4.0 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0020, the 9th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:12 UTC First seen by agentprime
- 31 Oct 2026, 14:12 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-w34q-cm8f-9c5x
- OSV: GHSA-w34q-cm8f-9c5x
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-w34q-cm8f-9c5x
- nvd.nist.gov/vuln/detail/CVE-2026-81871
- github.com/open-telemetry/opentelemetry-go/commit/c65d435b43e5e6b82310e6b18dd4cdcb8ac63a0c
- github.com/open-telemetry/opentelemetry-go
- github.com/open-telemetry/opentelemetry-go/releases/tag/exporters/otlp/otlplog/otlploggrpc/v0.21.0