CVE-2026-39882Public exploit

Process crash via unbounded exporter response buffering

Published Apr 8, 2026 · Updated Apr 8, 2026

Resource exhaustion in OpenTelemetry-Go before 1.43.0 allows attackers to crash instrumented processes via malicious collector responses. OTLP HTTP trace, metric, and log exporter clients pass the entire resp.Body to io.Copy into an in-memory bytes.Buffer without a size limit on success and error paths. Exploitation requires an attacker-controlled collector endpoint or a man-in-the-middle position on the exporter connection; attacker-chosen response size drives heap growth and an out-of-memory process crash.

CVSS severity5.3
Medium
EPSS probability0.19%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Resource exhaustion in OpenTelemetry-Go before 1.43.0 allows attackers to crash instrumented processes via malicious collector responses. OTLP HTTP trace, metric, and log exporter clients pass the entire resp.Body to io.Copy into an in-memory bytes.Buffer without a size limit on success and error paths. Exploitation requires an attacker-controlled collector endpoint or a man-in-the-middle position on the exporter connection; attacker-chosen response size drives heap growth and an out-of-memory process crash.

The record

CVE
CVE-2026-39882
Published
Apr 8, 2026
Updated
Apr 8, 2026
Vendor
OpenTelemetry
Product
OpenTelemetry-Go
Classifications
CWE-789, T1499.004
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Apr 8, 2026CVE publishedPublication date reported by the CVE source.
  2. Apr 8, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=< 1.43.0

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

OpenTelemetry · OpenTelemetry-Goversion=< 1.43.0

Published CVSS scores

5.3GitHub, Inc.CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-789Memory Allocation with Excessive Size Value
T1499.004Application or System Exploitation

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo