OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to version 0.21.0, the go.opentelemetry.io/otel/sdk/log BatchingProcessor can enter a tight CPU loop when attacker-driven log emission fills its asynchronous export buffer while the exporter is backpressured. NewBatchingProcessor wraps the exporter with newBufferExporter(exporter, 1), and the poll loop calls queue.TryDequeue and bufferExporter.EnqueueExport before immediately signaling pollTrigger whenever the queue remains at or above batchSize. Because a failed nonblocking EnqueueExport leaves the queue length unchanged, the processor repeatedly retries without waiting for its ticker, exhausting CPU and degrading or denying service in the embedding process. This issue is fixed in version 0.21.0.
CVE-2026-81872
“—” beside the score: it is equal to the CVSS score beside it.
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (32nd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-81261 (ENISA EUVD) · GHSA-hjf4-fphr-2h65 (GitHub Security Advisories) · GO-2026-6615 (OSV.dev)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 6.3
- EG Score
- 6.3MEDIUMmedium confidence
- EG Risk
- 44EG Risk 44/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)Severity63% × 45%Impact severity (EG Severity): CVSS 6.3 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.4%
- EPSS %ILE
- 32nd
- 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 (6.3): severity, escalated by confirmed exploitation. This CVE's 6.3 is its impact severity (EG Severity), not escalated.
- EG Severity
- 6.3 MEDIUMCVSS-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.4% 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
Advisory Details (4)
Auto-updated Sep 16, 2026commit ba71b09e6ed2 (open-telemetry/opentelemetry-go)
Fix landed in open-telemetry/opentelemetry-go commit ba71b09e6ed2 — awaiting tagged release
https://github.com/open-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aeaec1e98b1df4cc582sdk/log: prevent BatchProcessor busy-spin
Fix merged in open-telemetry/opentelemetry-go PR #8620 on 2026-07-24 — awaiting tagged release
https://github.com/open-telemetry/opentelemetry-go/pull/8620sdk/log: Redesign BatchProcessor · Issue #6797 · open-telemetry/opentelemetry-go · GitHub
https://github.com/open-telemetry/opentelemetry-go/issues/6797BatchProcessor can busy-spin when export buffer is full · Advisory · open-telemetry/opentelemetry-go · GitHub
https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2h65Vendor Advisories for CVE-2026-81872(10)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
- GHSA-hjf4-fphr-2h65GitHub Security AdvisoriesMedium
OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full
- CVE-2026-81872Microsoft Security Response Center (MSRC)Low
OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full
- RHSA-2026:68926Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:68821Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:68778Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:68729Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:68717Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update
- RHSA-2026:68591Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update
- +2 more
Patch Availability(13)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | grafana12-4-main-12.4.10-0.6.hum1 | 2026-09-18 | redhat |
| redhat | opentofu1-12-main-1.12.6-0.3.hum1 | 2026-09-18 | redhat |
| redhat | jaeger-main-2.20.0-0.9.hum1 | 2026-09-18 | redhat |
| redhat | grafana13-1-main-13.1.6-0.2.hum1 | 2026-09-18 | redhat |
| redhat | grafana13-2-main-13.2.1-0.5.hum1 | 2026-09-17 | redhat |
| redhat | helm3-main-3.22.0-0.2.hum1 | 2026-09-17 | redhat |
| redhat | helm4-main-4.3.0-0.2.hum1 | 2026-09-17 | redhat |
| redhat | opentelemetry-collector-k8s-main-0.161.0-0.1.hum1 | 2026-09-17 | redhat |
| redhat | caddy-main-2.11.4-0.4.hum1 | 2026-09-17 | redhat |
| redhat | distribution-main-3.1.1-0.2.hum1 | 2026-09-17 | redhat |
| redhat | opentelemetry-collector-contrib-main-0.161.0-0.1.hum1 | 2026-09-16 | redhat |
| redhat | opentelemetry-collector-main-0.161.0-0.1.hum1 | 2026-09-16 | redhat |
| go | go.opentelemetry.io/otel/sdk/log @ 0.21.0 (fixes < 0.21.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
(3 across 3 ecosystems)
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-opentelemetry-otel | 1.31.0-4 ... 1.46.0-2 (9 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| golang-opentelemetry-otel | 1.31.0-4 ... 1.46.0-2 (9 versions) |
| — |
Go(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| go.opentelemetry.io/otel/sdk/log | — |
| — |
Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Additional Vendor Advisories
(4)
Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.
Data Freshness Timeline
(refreshed 10× in last 7d / 58× 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.
Showing the most recent 100 of 108 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 8 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-11-01 07:38 UTCGHSA enrichmentGHSA-hjf4-fphr-2h65 · GitHub severity MODERATE
- 2026-11-01 07:38 UTCEG score recompute
- 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-30 01:55 UTCOSV refresh
- 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
- 2026-10-25 13:58 UTCEG score recompute
- 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-22 13:46 UTCEG score recompute
- 2026-10-22 13:46 UTCVendor advisory
- 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
- 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-18 03:09 UTCEG score recompute
- 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
Show 75 moreShow fewer
- 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-12 14:56 UTCEG score recompute
- 2026-10-11 20:53 UTCVendor advisory
- 2026-10-11 19:20 UTCEG score recompute
- 2026-10-11 16:36 UTCEG score recompute
- 2026-10-11 13:54 UTCEG score recompute
- 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-10 22:41 UTCEG score recompute
- 2026-10-10 22:41 UTCVendor advisory
- 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-09 23:32 UTCEG score recompute
- 2026-10-09 23:32 UTCVendor advisory
- 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-09 01:25 UTCEG score recompute
- 2026-10-09 01:25 UTCVendor advisory
- 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-08 03:19 UTCEG score recompute
- 2026-10-08 03:19 UTCVendor advisory
- 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-07 05:11 UTCEG score recompute
- 2026-10-07 05:11 UTCVendor advisory
- 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-06 07:04 UTCEG score recompute
- 2026-10-06 07:04 UTCVendor advisory
- 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-05 08:24 UTCEG score recompute
- 2026-10-05 08:24 UTCVendor advisory
- 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-04 10:17 UTCEG score recompute
- 2026-10-04 10:17 UTCVendor advisory
- 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 30th percentile
- 2026-10-03 12:10 UTCEG score recompute
- 2026-10-03 12:10 UTCVendor advisory
- 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-02 14:03 UTCEG score recompute
- 2026-10-02 14:03 UTCVendor advisory
- 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-10-01 15:56 UTCVendor advisory
- 2026-09-30 17:50 UTCEG score recompute
- 2026-09-30 17:50 UTCVendor advisory
- 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.4% · 29th percentile
- 2026-09-30 12:24 UTCEG score recompute
- 2026-09-30 12:24 UTCVendor advisory
- 2026-09-29 14:17 UTCEG score recompute
- 2026-09-29 14:17 UTCVendor advisory
- 2026-09-28 16:10 UTCEG score recompute
- 2026-09-28 16:10 UTCVendor advisory
- 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-27 17:58 UTCEG score recompute
- 2026-09-27 17:58 UTCVendor advisory
- 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-26 19:51 UTCEG score recompute
- 2026-09-26 19:51 UTCVendor advisory
- 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
- 2026-09-25 21:42 UTCVendor advisory
- 2026-09-24 23:25 UTCEG score recompute
- 2026-09-24 23:25 UTCVendor advisory
- 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 41st percentile
- 2026-09-24 01:18 UTCEG score recompute
- 2026-09-24 01:18 UTCVendor advisory
- 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-23 03:12 UTCEG score recompute
- 2026-09-23 03:12 UTCVendor advisory
- 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-22 05:05 UTCEG score recompute
- 2026-09-22 05:05 UTCVendor advisory
- 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.3% · 22nd percentile
- 2026-09-21 06:59 UTCEG score recompute
- 2026-09-21 06:59 UTCVendor advisory
- 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
- 2026-09-20 08:50 UTCEG score recompute
- 2026-09-20 08:50 UTCVendor advisory
- 2026-09-19 10:43 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same product
7 shownDebian:13:golang-opentelemetry-otel
Same vendor
10 shownredhat:RHSA-2026:68715 · redhat:RHSA-2026:68272 · redhat:RHSA-2026:68778
Frequently asked(5)
What is CVE-2026-81872?
When was the CVE record for CVE-2026-81872 published?
Is CVE-2026-81872 actively exploited?
What is the CVSS score of CVE-2026-81872?
How do I remediate CVE-2026-81872?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-81872
Is Your Infrastructure Affected by CVE-2026-81872?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.