CVE-2026-81870

LOWPre-NVD 2.02.0—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 4 sources updated this weekElevated
2.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.0Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
2.0
EG Score
2.0(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity20% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

September 16, 2026

Last Modified

September 17, 2026

References (6)

Vendor Advisories for CVE-2026-81870(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 1 ecosystem)
Go(5)
PackageVulnerable rangeFixed inDependents
go.opentelemetry.io/otel/exporters/otlp/otlptrace—1.45.0—
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc—1.45.0—
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp—1.45.0—
go.opentelemetry.io/otel/exporters/zipkin—1.45.0—
go.opentelemetry.io/otel/sdk—1.45.0—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 8× in last 7d / 8× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-20 13:18 UTCEG score recompute
  2. 2026-09-20 13:18 UTCVendor advisory
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 15:24 UTCEG score recompute
  5. 2026-09-17 15:04 UTCEG score recompute
  6. 2026-09-16 20:31 UTCEG score recompute
  7. 2026-09-16 20:09 UTCEG score recompute
  8. 2026-09-16 20:09 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-81870?
CVE-2026-81870 is a low vulnerability published on September 16, 2026. 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.…
When was CVE-2026-81870 disclosed?
CVE-2026-81870 was first published in the National Vulnerability Database on September 16, 2026, with the most recent update on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-81870 actively exploited?
CVE-2026-81870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 91.4% of all scored CVEs.
What is the CVSS score of CVE-2026-81870?
CVE-2026-81870 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-81870?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-81870, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81870

Explore →

Is Your Infrastructure Affected by CVE-2026-81870?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs