Skip to content

← Actionable
Medium, CVSS 6.3amended

OpenTelemetry-Go: Log gRPC exporter ignores env TLS certs, bypassing mTLS/pinning

CVE-2026-81871GHSA-w34q-cm8f-9c5x

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc 0.21.0), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.3 · 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 · score source
EPSS
  • CVE-2026-81871: 0.20% estimated exploitation activity in the next 30 days; percentile 9.42 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The OTLP log gRPC exporter loads TLS settings from environment variables but does not apply them when creating gRPC transport credentials. Operators who rely on OTELEXPORTEROTLPLOGSCERTIFICATE, OTELEXPORTEROTLPCERTIFICATE, or related client certificate variables for CA pinning or mTLS get a connection that falls back to system roots and omits the env-supplied client certificate. A network attacker who can intercept or spoof the collector connection with a system-trusted certificate can read or alter log telemetry. Introduced in commit: d99c76f Details The affected code is in exporters/otlp/otlplog/otlploggrpc. newConfig resolves env-based TLS configuration into cfg.tlsCfg at exporters/otlp/otlplog/otlploggrpc/config.go:106-116. The finding also identifies loadEnvTLS at config.go:451-492 as the code that builds a tls.Config containing RootCAs and client certificates from OTELEXPORTEROTLP[LOGS]CERTIFICATE and OTELEXPORTEROTLP[LOGS]CLIENTCERTIFICATE/KEY. However,…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-w34q-cm8f-9c5x

  2. Revision 3 · amended ·

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

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6508

  4. Revision 1 · created ·

    Published from osv record GHSA-w34q-cm8f-9c5x

Agent brief

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

# Patch Next advisory brief: CVE-2026-81871

Advisory: OpenTelemetry-Go: Log gRPC exporter ignores env TLS certs, bypassing mTLS/pinning
IDs: CVE-2026-81871, GHSA-w34q-cm8f-9c5x
Record: https://patchnext.com/advisories/cve-2026-81871 (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: Medium (CVSS 6.3)
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/otlplog/otlploggrpc 0.21.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: affected < 0.21.0; fixed in 0.21.0

## Suggested inspection (read-only)
- Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc: 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/otlplog/otlploggrpc.
- 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-w34q-cm8f-9c5x (OSV record GHSA-w34q-cm8f-9c5x lists affected ranges: Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc >=0 <0.21.0 (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6508 (OSV record GO-2026-6508 lists affected ranges: Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc >=0 <0.21.0 (fixed))
- Verified: https://github.com/advisories/GHSA-w34q-cm8f-9c5x (GitHub-reviewed advisory GHSA-w34q-cm8f-9c5x lists affected ranges: Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc >=0 <0.21.0)

Commands are suggestions: review each one before running it.

Loading voting…