Vulnerability in OpenTelemetry opentelemetry-exporter-otlp-proto-http (CVE-2026-112006)
Summary
Vulnerability in OpenTelemetry opentelemetry-exporter-otlp-proto-http (CVE-2026-112006). Risk of unauthorized operations or information disclosure.
Original description
The description as published by the source.
OpenTelemetry opentelemetry-exporter-otlp-proto-http 1.5.0 before 1.45.0 contains an improper certificate validation vulnerability that disables TLS verification when OTEL_EXPORTER_OTLP_CERTIFICATE variables are empty strings. Man-in-the-middle attackers can impersonate the collector to read or alter exported traces, metrics, and logs, including authentication headers from OTEL_EXPORTER_OTLP_HEADERS.
Source: GitHub Security Advisories (Global) 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-112006 has been found in OpenTelemetry opentelemetry-exporter-otlp-proto-http.
Risk of unauthorized operations or information disclosure.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "OpenTelemetry opentelemetry-exporter-otlp-proto-http CVE-2026-112006" on the vendor's site.
CVE-2026-112006 (OpenTelemetry opentelemetry-exporter-otlp-proto-http) — CWE-295
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.
A vulnerability (CWE-295) exists in OpenTelemetry opentelemetry-exporter-otlp-proto-http.
Check the vendor advisory for the affected versions of OpenTelemetry opentelemetry-exporter-otlp-proto-http.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで OpenTelemetry opentelemetry-exporter-otlp-proto-http を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。