Live › vulnerability › CVE-2026-81872
Go to dashboardThe OpenTelemetry Go log SDK's batch processor can enter a tight CPU loop when its export buffer is full and the exporter is backpressured. An attacker who can make the application emit many logs can exhaust CPU and degrade or deny service in the process.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| go.opentelemetry.io/otel/sdk/log | go | < 0.21.0 | 0.21.0 |
Run go list -m go.opentelemetry.io/otel/sdk/log in the service module and check whether the version is below 0.21.0.
Upgrade go.opentelemetry.io/otel/sdk/log to 0.21.0 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-81872")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.