CVE-2026-81872

OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full

CVE-2026-81872 is fixed in 3 products on 1 platform, first by DEBIAN-CVE-2026-81872, released September 16, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
Low
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0038
32nd percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
distribution · opensuse-leap 16.0 3.1.1-160000.4.1 OPENSUSE-SU-2026:22010-1 Oct 1, 2026
distribution · sles 16.0 3.1.1-160000.4.1 SUSE-SU-2026:23990-1 Oct 1, 2026
golang-opentelemetry-otel · Debian 14 1.46.0-2 DEBIAN-CVE-2026-81872 Sep 16, 2026
helm · opensuse-leap 16.0 4.3.0-160000.1.1 OPENSUSE-SU-2026:21983-1 Sep 30, 2026
helm · sles 15.6 3.22.1-150000.1.104.1 SUSE-SU-2026:5119-1 Nov 7, 2026
helm · sles 15.7 3.22.1-150000.1.104.1 SUSE-SU-2026:5119-1 Nov 7, 2026
helm · sles 16.0 4.3.0-160000.1.1 SUSE-SU-2026:23984-1 Sep 30, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.