Vulnerability in OpenTelemetry.Exporter.Instana (CVE-2026-44213)
Summary
Vulnerability in OpenTelemetry.Exporter.Instana (CVE-2026-44213). Confidential information can be exposed externally. Exploitable via OpenTelemetry.Exporter.Instana. Mitigation: upgrade to 1.1.0 or later.
Original description
The description as published by the source.
The OpenTelemetry.Exporter.Instana exports telemetry to Instana backend. Prior to 1.1.0, the OpenTelemetry.Exporter.Instana NuGet package does not validate HTTPS/TLS certificates are valid when sending telemetry to a configured Instana back-end when a proxy is configured using the INSTANA_ENDPOINT_PROXY environment variable. If a network attacker can Man-in-the-Middle (MitM) the proxy connection, all OpenTelemetry telemetry data and the Instana API key are exposed to the attacker. This vulnerability is fixed in 1.1.0.
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-44213 has been found in OpenTelemetry.Exporter.Instana.
Attackers can target a specific entry point like OpenTelemetry.Exporter.Instana over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.5/10.
What to do: upgrade OpenTelemetry.Exporter.Instana to 1.1.0 or later.
If unsure, ask your IT team or search "OpenTelemetry.Exporter.Instana CVE-2026-44213" on the vendor's site.
CVE-2026-44213 (OpenTelemetry.Exporter.Instana) — CWE-295 / CVSS v3 6.5
Attack vector: remote (network-reachable) / no user interaction
Attack surface: OpenTelemetry.Exporter.Instana / INSTANA_ENDPOINT_PROXY / HttpClient
Patched: 1.1.0 — apply immediately
Workaround: Do not configure the INSTANA_ENDPOINT_PROXY environment variable.
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.Exporter.Instana. Attackers reach the vulnerable code path via OpenTelemetry.Exporter.Instana.
Check the vendor advisory for the affected versions of OpenTelemetry.Exporter.Instana. Attack surface: OpenTelemetry.Exporter.Instana / INSTANA_ENDPOINT_PROXY / HttpClient.
Severity: Medium (CVSS 6.5/10). Confidential information can be exposed externally.
Update to 1.1.0.
Workaround: Do not configure the INSTANA_ENDPOINT_PROXY environment variable.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'OpenTelemetry.Exporter.Instana' . 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
-
1Identify exposure identify
grep -r 'OpenTelemetry.Exporter.Instana' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
OpenTelemetry.Exporter.Instanaを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Do not configure the `INSTANA_ENDPOINT_PROXY` environment variable.パッチが適用されるまでの応急処置として、Do not configure the
INSTANA_ENDPOINT_PROXYenvironment variable. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade OpenTelemetry.Exporter.Instana to 1.1.0ステージング環境で 1.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web github.com