MediumCVE-2026-81872

    OpenTelemetry-Go: BatchProcessor can busy-spin when export buffer is full (CVE-2026-81872)

    Published Last modified Sources: Red Hat, SUSE, OSV, Hersteller, CVE.org, Msrc Update Guide

    What is affected, what to do

    A flaw was found in the OpenTelemetry-Go `BatchingProcessor` component. A remote attacker can exploit this by sending a high volume of log emissions, which can fill the asynchronous export buffer.

    Update Opentelemetry-go to version 0.21.0.

    Affected
    • Opentelemetry-go lt *..0.21.0
    Fixed in
    • Opentelemetry-go 0.21.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    6.3

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: Vendor (CNA), CVSS v4

    6.3

    CVSS v4

    Severity Medium on the scale from 0 to 10.

    Source: Red Hat, SUSE, OSV, Hersteller, CVE.org, Msrc Update Guide

    0.4 %

    EPSS score

    Low — model estimates < 1% exploitation likelihood.

    Source: FIRST EPSS, percentile 32.3

    Show all metrics
    Severity
    Medium
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    67.27 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    no public PoC known
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    6.3 Methodology
    CVSS v4

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    6.3
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    0.4 %
    Low — model estimates < 1% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    32.3
    Elevated — this CVE ranks above at least 10% of all CVEs scored today.
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    —
    Published
    CISA assessment (SSVC)
    Exploitation: proof of concept · not automatable · Technical impact: partial
    Source: CISA Vulnrichment, as of 17 September 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-400, CWE-834

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Handle the vulnerability in regular vulnerability handling under Art. 21(2)(e) NIS2.
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    A flaw was found in the OpenTelemetry-Go `BatchingProcessor` component. A remote attacker can exploit this by sending a high volume of log emissions, which can fill the asynchronous export buffer. This causes the processor to enter a tight CPU loop, repeatedly retrying to export logs without proper waiting mechanisms. The consequence is the exhaustion of CPU resources, leading to a degradation or denial of service (DoS) in the affected application.

    Source: redhat_csaf, suse_csaf, OSV (Open Source Vulnerabilities), GitHub Security Advisories, NVD (NIST), cvelistv5, Microsoft Security Update Guide

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    open-telemetryopentelemetry-go
    • < 0.21.0
    • 0.21.0
    gogo.opentelemetry.io/otel/sdk/log
    • —
    • —

    Vendors and products

    Weakness classes (CWE)

    • CWE-400Uncontrolled Resource Consumption

      Class

      The product does not properly control the allocation and maintenance of a limited resource.

      Entry at MITRE CWE-400

    • CWE-834Excessive Iteration

      Class

      The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.

      Entry at MITRE CWE-834

    References & sources

    • github.comopen-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-f…x_refsource_CONFIRM
    • github.comopen-telemetry/opentelemetry-go/issues/6797x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/pull/8620x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aea…x_refsource_MISC
    • github.comopen-telemetry/opentelemetry-go/releases/tag/sdk/log/v0.21.0x_refsource_MISC
    • NVD (NIST)vuln/detail/CVE-2026-81872advisory
    • github.comopen-telemetry/opentelemetry-gopackage

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. Record modifiedCISA ADP

      CISA assessment (SSVC): exploitation: proof of concept, automatable: no

      Show 2 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2h65
      SSVC assessmentadded
      —
      {"id":"CVE-2026-81872","role":"CISA Coordinator","options":[{"exploitation":"poc"},{"automatable":"no"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-09-17T13:36:11.140898Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    2. ReceivedGitHub

      CVSS V4.0: AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N

      Weakness type: CWE-400, CWE-834

      Description added or changed

      Show 10 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Descriptionadded
      —
      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.
      CVSSadded
      —
      AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
      Weakness type (CWE)added
      —
      CWE-400
      Weakness type (CWE)added
      —
      CWE-834
      Affected versions (publisher)added
      —
      New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/81xxx/CVE-2026-81872.json">CVE-2026-81872</a>
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/commit/ba71b09e6ed272e93a669aeaec1e98b1df4cc582
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/issues/6797
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/pull/8620
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/releases/tag/sdk/log/v0.21.0
      Referenceadded
      —
      https://github.com/open-telemetry/opentelemetry-go/security/advisories/GHSA-hjf4-fphr-2h65

      Source identifier: security-advisories@github.com

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2026-81872
    <a href="https://intel.neosec.eu/en/cve/CVE-2026-81872"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-81872.svg?lang=en" alt="CVE-2026-81872 – NEOSEC Intel" height="20"></a>