LowCVE-2026-81870

    OpenTelemetry-Go: Exporter config logging may leak endpoint URLs in info logs (CVE-2026-81870)

    Published Last modified Sources: Red Hat, SUSE, OSV, CVE.org, Hersteller, Msrc Update Guide

    What is affected, what to do

    A flaw was found in OpenTelemetry-Go. The `sdk/trace.NewTracerProvider` component emits an internal Info-level diagnostic event that recursively includes span processor, exporter, and client configuration.

    The available sources name no fixed version. Check the vendor guidance in the references below.

    Affected
    • Opentelemetry-go gte 1.5.0, < 1.45.0..*

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    2.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    2.0

    CVSS v4

    Severity Low on the scale from 0 to 10.

    Source: Red Hat, SUSE, OSV, CVE.org, Hersteller, Msrc Update Guide

    0.3 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 18.5

    Show all metrics
    Severity
    Low
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    40.19 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    2.0 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    2.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.3 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    18.5
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: proof of concept · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 17 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-200, CWE-532

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A flaw was found in OpenTelemetry-Go. The `sdk/trace.NewTracerProvider` component emits an internal Info-level diagnostic event that recursively includes span processor, exporter, and client configuration. If an application enables OpenTelemetry internal Info logging, a person or system with access to those logs could learn internal collector topology and potentially recover credentials or tokens embedded in Zipkin URL user information or query strings. This vulnerability leads to information disclosure of sensitive configuration data.

    Source: redhat_csaf, suse_csaf, OSV (Open Source Vulnerabilities), NVD (NIST), GitHub Security Advisories, cvelistv5, Microsoft Security Update Guide

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    open-telemetryopentelemetry-go
    • ≥ 1.5.0, < 1.45.0
    • —
    gogo.opentelemetry.io/otel/exporters/otlp/otlptrace
    • 1.5.0
    • —
    gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc
    • 1.5.0
    • —
    gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp
    • 1.5.0
    • —
    gogo.opentelemetry.io/otel/exporters/zipkin
    • 1.5.0
    • —
    gogo.opentelemetry.io/otel/sdk
    • 1.5.0
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-200Exposure of Sensitive Information to an Unauthorized Actor

      Class

      The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

      Entry at MITRE CWE-200

    • CWE-532Insertion of Sensitive Information into Log File

      Base

      The product writes sensitive information to a log file.

      Entry at MITRE CWE-532

    References & sources

    • github.comopen-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6…x_refsource_CONFIRM
    • github.comopen-telemetry/opentelemetry-go/pull/8438x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2…x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/releases/tag/exporters/zipkin/v…x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/releases/tag/sdk/v1.45.0x_refsource_MISC
    • NVD (NIST)vuln/detail/CVE-2026-81870advisory
    • github.comopen-telemetry/opentelemetry-gopackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6v46-5gfg
      SSVC assessmentadded
      —
      {"id":"CVE-2026-81870","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-17T14:57:11.645138Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V4.0: AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

      Weakness type: CWE-200, CWE-532

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      OpenTelemetry-Go is the Go implementation of OpenTelemetry. From version 1.5.0 to 1.44.0, sdk/trace.NewTracerProvider emits a TracerProvider created internal Info-level diagnostic event whose MarshalLog implementations recursively include span processor, exporter, and client configuration. Applications that call otel.SetLogger to enable OpenTelemetry internal Info logging can therefore record OTLP gRPC and HTTP collector endpoints, the OTLP HTTP Insecure flag, and complete Zipkin collector URLs. A person or system with access to those logs can learn internal collector topology and can recover credentials or tokens embedded in Zipkin URL user information or query strings. The default OpenTelemetry logger does not emit the event, and this path does not log OTLP authentication headers, TLS key material, or span payloads. This issue is fixed in version 1.45.0.
      CVSSadded
      —
      AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-200
      Weakness type (CWE)added
      —
      CWE-532
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/81xxx/CVE-2026-81870.json">CVE-2026-81870</a>
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/commit/3a1412d2b3bc4e4231fbeac2ed42117ae541bb38
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/pull/8438
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/releases/tag/exporters/zipkin/v1.45.0
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/v1.45.0
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-8wmf-6v46-5gfg

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-81870
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-81870"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-81870.svg?lang=en" alt="CVE-2026-81870 – NEOSEC Intel" height="20"></a>