Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-wfr5-454p-mjc2 | OpenTelemetry.Exporter.Instana bypasses TLS certificate validation when a proxy is configured |
Wed, 27 May 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 26 May 2026 22:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry
Opentelemetry opentelemetry-dotnet-contrib |
|
| Vendors & Products |
Opentelemetry
Opentelemetry opentelemetry-dotnet-contrib |
Tue, 26 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | OpenTelemetry.Exporter.Instana bypasses TLS certificate validation when a proxy is configured | |
| Weaknesses | CWE-295 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-27T15:51:25.352Z
Reserved: 2026-05-05T15:13:47.572Z
Link: CVE-2026-44213
Updated: 2026-05-27T15:50:08.669Z
Status : Awaiting Analysis
Published: 2026-05-26T22:16:42.443
Modified: 2026-06-17T10:50:21.993
Link: CVE-2026-44213
No data.
OpenCVE Enrichment
Updated: 2026-05-26T22:30:18Z
Github GHSA