# OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs Advisory record · `GHSA-8wmf-6v46-5gfg` - **Identifiers:** `GHSA-8wmf-6v46-5gfg` · `CVE-2026-81870` · `GO-2026-6505` - **State:** Confirmed - **Severity:** CVSS 2.0 Low - **Critical:** No - **Weakness (CWE):** [CWE-200](https://cwe.mitre.org/data/definitions/200.html) · [CWE-532](https://cwe.mitre.org/data/definitions/532.html) - **Tags:** [Information disclosure](https://agentprime.io/advisories/tag/info-disclosure.md) - **Published:** 17 Sept 2026 - **Updated:** 1 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 17 Sept 2026, 20:31 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `go.opentelemetry.io/otel/sdk` (Go): affected `>=1.5.0, <1.45.0`; fixed in `1.45.0` - `go.opentelemetry.io/otel/exporters/otlp/otlptrace` (Go): affected `>=1.5.0, <1.45.0`; fixed in `1.45.0` - `go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc` (Go): affected `>=1.5.0, <1.45.0`; fixed in `1.45.0` - `go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp` (Go): affected `>=1.5.0, <1.45.0`; fixed in `1.45.0` - `go.opentelemetry.io/otel/exporters/zipkin` (Go): affected `>=1.5.0, <1.45.0`; fixed in `1.45.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > OpenTelemetry Go modules sdk, otlptrace, otlptracegrpc, otlptracehttp and zipkin exporter, versions 1.5.0 through 1.44.0, log the trace exporter endpoint configuration at Info level when a TracerProvider is created. An attacker with access to those logs can learn the collector address and whether OTLP/HTTP is insecure, and any credentials or tokens embedded in a Zipkin collector URL. Exposure requires the application to enable verbose internal diagnostics. Upgrade to version 1.45.0 or later; until then, keep internal logging below Info verbosity and avoid putting credentials in endpoint URLs. Written 1 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 2.0 Low, CVSS 4.0: `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`, from CNA (GitHub_M) - **CISA KEV:** Not listed. - **EPSS:** 0.0027, the 18th percentile, on 8 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:12 UTC: First seen by agentprime - 31 Oct 2026, 14:12 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-8wmf-6v46-5gfg) ## Sources - [GitHub Advisory Database: GHSA-8wmf-6v46-5gfg](https://github.com/advisories/GHSA-8wmf-6v46-5gfg) - [OSV: GHSA-8wmf-6v46-5gfg](https://osv.dev/vulnerability/GHSA-8wmf-6v46-5gfg) - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .