← Back
CVE-2026-42191
medium
CVSS 6.5
Vulnerability in OpenTelemetry.Exporter.OpenTelemetryProtocol (CVE-2026-42191)
Summary
vulnerability in OpenTelemetry.Exporter.OpenTelemetryProtocol (CVE-2026-42191). Confidential information can be exposed externally. Exploitable via ``traces``. Mitigation: upgrade to `1.15.3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-42191** has been found in OpenTelemetry.Exporter.OpenTelemetryProtocol.
Attackers can target a specific entry point like ``traces`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade OpenTelemetry.Exporter.OpenTelemetryProtocol to **1.15.3** or later.
If unsure, ask your IT team or search "OpenTelemetry.Exporter.OpenTelemetryProtocol CVE-2026-42191" on the vendor's site.
CVE-2026-42191 (OpenTelemetry.Exporter.OpenTelemetryProtocol) — CWE-379 / CVSS v3 6.5
Attack vector: local / no user interaction
Attack surface: `traces` / `metrics` / `logs` / `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY`
Patched: `1.15.3` — 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-379) exists in OpenTelemetry.Exporter.OpenTelemetryProtocol. Attackers reach the vulnerable code path via ``traces`` without authentication.
📍 Affected scope
OpenTelemetry.Exporter.OpenTelemetryProtocol — . Attack surface: `traces` / `metrics` / `logs` / `OTEL_DOTNET_EXPERIMENTAL_OTLP_RETRY`.
🔥 Severity
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally
🔧 How to fix
Update to **1.15.3**.
🛡️ 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 'OpenTelemetry.Exporter.OpenTelemetryProtocol' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'OpenTelemetry.Exporter.OpenTelemetryProtocol' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `OpenTelemetry.Exporter.OpenTelemetryProtocol` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade OpenTelemetry.Exporter.OpenTelemetryProtocol to 1.15.3ステージング環境で 1.15.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
nuget
OpenTelemetry.Exporter.OpenTelemetryProtocol
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.15.3"}]}]