Skip to content

← Public intelligence

NuGet package

opentelemetry.exporter.instana

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Medium, CVSS 6.5NuGetPublished

    OpenTelemetry.Exporter.Instana bypasses TLS certificate validation when a proxy is configured

    CVE-2026-44213 · GHSA-wfr5-454p-mjc2

    Affected
    • NuGet opentelemetry.exporter.instana <= 1.0.7
    Fixed in
    1.1.0· Vendor fix available
    Issue
    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 INSTANAENDPOINTPROXY 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. Details The Transport.ConfigureBackendClient() method creates an HttpClient instance that completely disables TLS server certificate validation if the INSTANAENDPOINTPROXY is configured with a valid proxy URL with no ability to re-enable it. Impact If the configured proxy is attacker-controlled (or a network attacker MitM the connection), or if it is possible for the process' configuration to be changed to add an attacker-provided value for INSTANAENDPOINTPROXY then all Instana telemetry could be read by an unauthorized party and the service's Instana API key compromised, potentially…

    Recommended action: Upgrade to 1.1.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →