GHSA-wfr5-454p-mjc2

Suggest an improvement
Source
https://github.com/advisories/GHSA-wfr5-454p-mjc2
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-wfr5-454p-mjc2/GHSA-wfr5-454p-mjc2.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-wfr5-454p-mjc2
Aliases
  • CVE-2026-44213
Published
2026-05-08T20:48:02Z
Modified
2026-05-08T21:04:45.614581Z
Severity
  • 6.5 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N CVSS Calculator
Summary
OpenTelemetry.Exporter.Instana bypasses TLS certificate validation when a proxy is configured
Details

Summary

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.

Details

The Transport.ConfigureBackendClient() method creates an HttpClient instance that completely disables TLS server certificate validation if the INSTANA_ENDPOINT_PROXY 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 INSTANA_ENDPOINT_PROXY then all Instana telemetry could be read by an unauthorized party and the service's Instana API key compromised, potentially before being forwarded to Instana presenting no noticeable loss of telemetry data without a valid TLS server certificate being presented to the client that matches the expected hostname or IP address.

Mitigation

The proxy configured by the INSTANA_ENDPOINT_PROXY environment variable must be malicious or be possible to be subject to a MitM attack.

Workarounds

Do not configure the INSTANA_ENDPOINT_PROXY environment variable.

Remediation

#4153 refactors HttpClient creation so that TLS certificate validation is no longer disabled by default when using a proxy.

In environments where this capability is required, for example for local development, the previous behaviour can be restored using the `` option:

builder.AddInstanaExporter((options) =>
{
    options.HttpClientFactory = () =>
    {
        var handler = new HttpClientHandler()
        {
#if NET
            ServerCertificateCustomValidationCallback = HttpClientHandler.DangerousAcceptAnyServerCertificateValidator,
#else
            ServerCertificateCustomValidationCallback = static (_, _, _, _) => true,
#endif
        };
        return new HttpClient(handler, disposeHandler: true);
    };
});

Resources

Database specific
{
    "github_reviewed": true,
    "github_reviewed_at": "2026-05-08T20:48:02Z",
    "cwe_ids": [
        "CWE-295"
    ],
    "severity": "MODERATE",
    "nvd_published_at": null
}
References

Affected packages

NuGet / OpenTelemetry.Exporter.Instana

Package

Name
OpenTelemetry.Exporter.Instana
View open source insights on deps.dev
Purl
pkg:nuget/OpenTelemetry.Exporter.Instana

Affected ranges

Type
ECOSYSTEM
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.1.0

Affected versions

1.*
1.0.0
1.0.1
1.0.2
1.0.3
1.0.4
1.0.5
1.0.6
1.0.7

Database specific

source
"https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/05/GHSA-wfr5-454p-mjc2/GHSA-wfr5-454p-mjc2.json"
last_known_affected_version_range
"<= 1.0.7"