Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-81871

Vulnerability in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc (CVE-2026-81871)

Summary

Vulnerability in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc (CVE-2026-81871). Risk of unauthorized operations or information disclosure. Exploitable via OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE. Mitigation: upgrade to 0.21.0 or later.

Original description

The description as published by the source.

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 OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE, OTEL_EXPORTER_OTLP_CERTIFICATE, 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 OTEL_EXPORTER_OTLP[_LOGS]_CERTIFICATE and OTEL_EXPORTER_OTLP[_LOGS]_CLIENT_CERTIFICATE/KEY.

However, newGRPCDialOptions in exporters/otlp/otlplog/otlploggrpc/client.go:83-92 only checks cfg.gRPCCredentials and cfg.insecure. When neither is set, which is the normal env-only TLS configuration path, it uses credentials.NewTLS(nil). That default trusts the host system root CAs and contains no env-supplied client certificate. The finding evidence reports no other tlsCfg use in the package, so env-based CA pinning and mTLS settings are loaded but n…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-81871 has been found in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc.
Attackers can target a specific entry point like OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc to 0.21.0 or later.
If unsure, ask your IT team or search "go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc CVE-2026-81871" on the vendor's site.

CVE-2026-81871 (go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc) — CWE-295
Attack surface: OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE / OTEL_EXPORTER_OTLP_CERTIFICATE / newConfig / cfg.tlsCfg
Patched: 0.21.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-295) exists in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc. Attackers reach the vulnerable code path via OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE.

📍 Affected scope

Check the vendor advisory for the affected versions of go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc. Attack surface: OTEL_EXPORTER_OTLP_LOGS_CERTIFICATE / OTEL_EXPORTER_OTLP_CERTIFICATE / newConfig / cfg.tlsCfg.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.21.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc to 0.21.0

    ステージング環境で 0.21.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.21.0"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details