CVE-2026-81870

LOWPre-NVD 2.02.0
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This low-severity CVE scores 2.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (18th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 5 sources updated this weekElevated

Also known asEUVD-2026-81098 (ENISA EUVD) · GHSA-8wmf-6v46-5gfg (GitHub Security Advisories) · GO-2026-6505 (OSV.dev)Source: ENISA EUVD

2.0EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 2.0Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.0LOWmedium confidence
EG Risk
25
EG Risk 25/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity20% × 45%
Impact severity (EG Severity): CVSS 2.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (2.0): severity, escalated by confirmed exploitation. This CVE's 2.0 is its impact severity (EG Severity), not escalated.

EG Severity
2.0 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 16, 2026

Last Modified

September 30, 2026

References (5)

Vendor Advisories for CVE-2026-81870(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcert-manager/cert-manager-istio-csr-rhel9:17902237192026-09-28redhat
redhatcert-manager/cert-manager-istio-csr-rhel9:17905899142026-09-28redhat
gogo.opentelemetry.io/otel/exporters/otlp/otlptrace @ 1.45.0 (fixes >= 1.5.0, <= 1.44.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(7 across 3 ecosystems)
Go(5)
PackageVulnerable rangeFix by version rangeDependents
go.opentelemetry.io/otel/exporters/otlp/otlptrace—
  • 1.5.0 up to 1.45.0: fixed in 1.45.0
—
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc—
  • 1.5.0 up to 1.45.0: fixed in 1.45.0
—
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp—
  • 1.5.0 up to 1.45.0: fixed in 1.45.0
—
go.opentelemetry.io/otel/exporters/zipkin—
  • 1.5.0 up to 1.45.0: fixed in 1.45.0
—
go.opentelemetry.io/otel/sdk—
  • 1.5.0 up to 1.45.0: fixed in 1.45.0
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-2 (9 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
golang-opentelemetry-otel1.31.0-4 ... 1.46.0-2 (9 versions)
  • every version on: no fix on record
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 47× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-01 07:38 UTCGHSA enrichmentGHSA-8wmf-6v46-5gfg · GitHub severity LOW
  3. 2026-11-01 07:38 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-10-29 17:45 UTCEG score recompute
  7. 2026-10-29 17:45 UTCVendor advisory
  8. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-27 05:55 UTCOSV refresh
  12. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-10-25 13:58 UTCEG score recompute
  15. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  17. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  18. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  21. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  22. 2026-10-18 03:09 UTCEG score recompute
  23. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
Show 48 more
  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  2. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  3. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  4. 2026-10-12 14:56 UTCEG score recompute
  5. 2026-10-11 19:20 UTCEG score recompute
  6. 2026-10-11 16:36 UTCEG score recompute
  7. 2026-10-11 13:54 UTCEG score recompute
  8. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  10. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  11. 2026-10-09 13:38 UTCEG score recompute
  12. 2026-10-09 13:38 UTCVendor advisory
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  15. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  16. 2026-10-06 13:57 UTCEG score recompute
  17. 2026-10-06 13:57 UTCVendor advisory
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  20. 2026-10-03 16:02 UTCEG score recompute
  21. 2026-10-03 16:02 UTCVendor advisory
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  23. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  24. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  25. 2026-09-30 18:08 UTCEG score recompute
  26. 2026-09-30 18:08 UTCVendor advisory
  27. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  28. 2026-09-29 07:08 UTCEG score recompute
  29. 2026-09-29 07:08 UTCVendor advisory
  30. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  31. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  32. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  33. 2026-09-26 09:11 UTCEG score recompute
  34. 2026-09-26 09:11 UTCVendor advisory
  35. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  36. 2026-09-23 11:13 UTCEG score recompute
  37. 2026-09-23 11:13 UTCVendor advisory
  38. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  39. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  40. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  41. 2026-09-20 13:18 UTCEG score recompute
  42. 2026-09-20 13:18 UTCVendor advisory
  43. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  44. 2026-09-17 15:24 UTCEG score recompute
  45. 2026-09-17 15:04 UTCEG score recompute
  46. 2026-09-16 20:31 UTCEG score recompute
  47. 2026-09-16 20:09 UTCEG score recomputeFirst assessed: 2.0 LOW
  48. 2026-09-16 20:09 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same vendor + same CWE)

Same product

9 shown

Go:go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp · Go:go.opentelemetry.io/otel/sdk · Debian:13:golang-opentelemetry-otel

Frequently asked(5)

What is CVE-2026-81870?
CVE-2026-81870 is a low-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-81870 published?
The CVE record for CVE-2026-81870 was published on September 16, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 30, 2026; the record at its source may have been updated since.
Is CVE-2026-81870 actively exploited?
CVE-2026-81870 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-81870?
CVE-2026-81870 has a CVSS base score of 2.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-81870?
A fix for CVE-2026-81870 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-81870 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs