Vulnerabilities in pkg:golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
PACKAGECVE-2026-81870 is a LOW exporter config logging may leak vulnerability (CWE-532: Insertion of Sensitive Information into Log File) affecting OpenTelemetry-Go libraries in the Go ecosystem. The issue involves exporter config logging may leak endpoint urls in info logs. Remediation is available by upgrading affected packages to version 1.45.0.
pkg:golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
Vulnerability advisories affecting package pkg:golang/go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-8wmf-6v46-5gfg | CVE-2026-81870 | LOW | OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs |
CVE-2026-81870 at a Glance
How to Fix CVE-2026-81870
To remediate this vulnerability, upgrade all affected OpenTelemetry-Go dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
Upgrade go.opentelemetry.io/otel/sdk to 1.45.0
Upgrade go.opentelemetry.io/otel/exporters/otlp/otlptrace to 1.45.0
Upgrade go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc to 1.45.0
Upgrade go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp to 1.45.0
Upgrade go.opentelemetry.io/otel/exporters/zipkin to 1.45.0
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
inspect dependencies for go.opentelemetry.io/otel/sdk
How to Check if You Are Affected
To determine whether your application is affected by CVE-2026-81870, inspect your project dependencies for OpenTelemetry-Go:
inspect dependencies for go.opentelemetry.io/otel/sdk
Analyze the terminal output to locate any version of OpenTelemetry-Go in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.45.0), your application is affected.
Note: Verify declared build manifests and deployed runtime container environments.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-532: Insertion of Sensitive Information into Log File, where the product writes sensitive information to a log file. In OpenTelemetry-Go, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-81870 Affected OpenTelemetry-Go Versions
5 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
go.opentelemetry.io/otel/sdk
|
Go |
≥ 1.5.0
< 1.45.0
|
1.45.0
|
|
go.opentelemetry.io/otel/exporters/otlp/otlptrace
|
Go |
≥ 1.5.0
< 1.45.0
|
1.45.0
|
|
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
|
Go |
≥ 1.5.0
< 1.45.0
|
1.45.0
|
|
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
|
Go |
≥ 1.5.0
< 1.45.0
|
1.45.0
|
|
go.opentelemetry.io/otel/exporters/zipkin
|
Go |
≥ 1.5.0
< 1.45.0
|
1.45.0
|
References
Frequently Asked Questions
What is CVE-2026-81870?
Which OpenTelemetry-Go versions are affected?
What version fixes CVE-2026-81870?
Is go.opentelemetry.io/otel/sdk affected?
Is go.opentelemetry.io/otel/exporters/otlp/otlptrace affected?
What CWE is associated with CVE-2026-81870?
How can I check Go dependencies for CVE-2026-81870?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-8wmf-6v46-5gfg",
"modified" : "2026-09-17T20:31:06Z",
"published" : "2026-09-17T20:31:06Z",
"aliases" : [ "CVE-2026-81870" ],
"summary" : "OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs",
"details" : "### Summary\n\nOpenTelemetry Go versions 1.5.0 through 1.44.0 can include trace exporter endpoint configuration in an internal diagnostic log emitted when an SDK `TracerProvider` is created. The default OpenTelemetry logger does not emit this event. Exposure requires an application to install a logger that enables OpenTelemetry's internal Info-level diagnostics and for someone other than the intended audience to have access to those logs.\n\nThe logged configuration can disclose the address of the trace collector and whether the OTLP/HTTP connection is configured as insecure. The Zipkin exporter logs its complete collector URL, so credentials in URL userinfo or tokens in the query string are also disclosed if an application embeds them there. OTLP authentication headers, TLS key material, and exported span data are not included in this log.\n\nExporter `MarshalLog` implementations that caused this configuration to be included in internal logs were introduced by [`a1fff3c`](https://github.com/open-telemetry/opentelemetry-go/commit/a1fff3c2588c783d1f3f6fd2315aa2660fc6d330).\n\n### Details\n\nWhen `sdk/trace.NewTracerProvider` constructs a provider, it records a `TracerProvider created` internal Info event containing the provider configuration. In affected versions, the configuration's `MarshalLog` methods recursively include:\n\n1. the provider's span processors;\n2. each processor's span exporter; and\n3. for the OTLP trace exporter, its client configuration.\n\nThis causes the following values to be present in the event:\n\n- OTLP trace gRPC: the configured endpoint;\n- OTLP trace HTTP: the configured endpoint and the `Insecure` flag; and\n- Zipkin: the complete collector URL.\n\nOpenTelemetry Go does not emit this event with its default logger, which only emits errors. An application must explicitly configure a sufficiently verbose logger with `otel.SetLogger`. The required `logr` verbosity is version-dependent:\n\n- versions 1.5.0 through 1.14.x use `V(1)` for this Info event; and\n- versions 1.15.0 through 1.44.0 use `V(4)`.\n\nOTLP header configuration is not part of the marshaled object, so credentials supplied with `WithHeaders` or the corresponding environment variables are not exposed. The documented OTLP `WithEndpoint` input is a collector address rather than a credential-bearing URL. The higher-risk case is therefore the Zipkin collector URL, which is retained and logged in full, or an application passing sensitive data in an OTLP endpoint outside the documented format.\n\n### Proof of concept\n\nThe following program demonstrates the behavior with OpenTelemetry Go 1.44.0. It deliberately places credentials and a token in the Zipkin collector URL and enables internal Info logging:\n\n```go\npackage main\n\nimport (\n\t\"bytes\"\n\t\"context\"\n\t\"fmt\"\n\n\t\"github.com/go-logr/logr/funcr\"\n\t\"go.opentelemetry.io/otel\"\n\t\"go.opentelemetry.io/otel/exporters/zipkin\"\n\tsdktrace \"go.opentelemetry.io/otel/sdk/trace\"\n)\n\nfunc main() {\n\tvar logs bytes.Buffer\n\totel.SetLogger(funcr.New(func(_, args string) {\n\t\t_, _ = logs.WriteString(args)\n\t}, funcr.Options{Verbosity: 4}))\n\n\texporter, err := zipkin.New(\n\t\t\"http://user:pass@zipkin.internal:9411/api/v2/spans?token=secret\",\n\t)\n\tif err != nil {\n\t\tpanic(err)\n\t}\n\n\ttp := sdktrace.NewTracerProvider(sdktrace.WithBatcher(exporter))\n\t_ = tp.Shutdown(context.Background())\n\n\tfmt.Println(logs.String())\n}\n```\n\nThe `TracerProvider created` event contains:\n\n```text\nhttp://user:pass@zipkin.internal:9411/api/v2/spans?token=secret\n```\n\nFor versions before 1.15.0, set `funcr.Options{Verbosity: 1}` instead.\n\n### Impact\n\nThis is a conditional disclosure through application logs. Affected applications must enable verbose OpenTelemetry internal diagnostics and configure a trace exporter containing information they do not intend to expose to readers of those logs. In that configuration, a person or system with log access can learn the trace collector address and internal network topology. If credentials or tokens are embedded directly in a Zipkin collector URL, those values can also be recovered from the logs.\n\nThere is no exposure with the default OpenTelemetry logger, and the vulnerable log is generated from local application configuration rather than remotely supplied span data. OTLP authentication headers, certificate or private-key contents, and telemetry payloads are not logged by this path.\n\n### Remediation\n\nUpgrade the affected OpenTelemetry Go modules to version 1.45.0 or later. The fix in [`3a1412d`](https://github.com/open-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2ed42117ae541bb38) stops recursively marshaling exporter and client configuration and records their types instead.\n\nIf an immediate upgrade is not possible:\n\n- keep OpenTelemetry internal logging below the Info verbosity described above;\n- do not embed credentials or tokens in exporter endpoint URLs; use authentication headers or another supported credential mechanism; and\n- restrict access to existing logs and rotate any credentials that may already have been recorded.",
"severity" : [ {
"type" : "CVSS_V4",
"score" : "CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Go",
"name" : "go.opentelemetry.io/otel/sdk"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.0"
}, {
"fixed" : "1.45.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.44.0"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "go.opentelemetry.io/otel/exporters/otlp/otlptrace"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.0"
}, {
"fixed" : "1.45.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.44.0"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.0"
}, {
"fixed" : "1.45.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.44.0"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.0"
}, {
"fixed" : "1.45.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.44.0"
}
}, {
"package" : {
"ecosystem" : "Go",
"name" : "go.opentelemetry.io/otel/exporters/zipkin"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "1.5.0"
}, {
"fixed" : "1.45.0"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 1.44.0"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6v46-5gfg"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-81870"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-go/pull/8438"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2ed42117ae541bb38"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/open-telemetry/opentelemetry-go"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-go/releases/tag/exporters/zipkin/v1.45.0"
}, {
"type" : "WEB",
"url" : "https://github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/v1.45.0"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-200", "CWE-532" ],
"severity" : "LOW",
"github_reviewed" : true,
"github_reviewed_at" : "2026-09-17T20:31:06Z",
"nvd_published_at" : "2026-09-16T20:17:32Z"
}
}