Resource exhaustion in Open-Telemetry Opentelemetry-Go
CVE-2026-81872
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.
Vulnerability class: DoS (Denial of Service)
Published · last modified .
EPSS exploit prediction
EPSS: 0.004 (32.4th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 32nd percentile — 32.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.004 · newest: 0.004 · change: 0.000
Affected products
- Open-Telemetry Opentelemetry-Go — versions < 0.21.0
Weakness classification (CWE)
References
- github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2…
- github.com/open-telemetry/opentelemetry-go/issues/6797
- github.com/open-telemetry/opentelemetry-go/pull/8620
- github.com/open-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aeaec1e9…
- github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/log/v0.21.0