Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

cve-program · CVE-2026-39882

Published

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Read the publisher's advisory

euvd · EUVD-2026-20628

Published

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Read the publisher's advisory

nvd · CVE-2026-39882

Published

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Read the publisher's advisory

osv · GHSA-w8rr-5gcm-pp58

Published

overview: this report shows that the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory `bytes.Buffer` without a size cap. this is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). severity HIGH not claiming: this is a remote dos against every default deployment. claiming: if the exporter sends traces to an untrusted collector endpoint (or over a network segment where mitm is realistic), that endpoint can crash the process via a large response body. callsite (pinned): - exporters/otlp/otlptrace/otlptracehttp/client.go:199 - exporters/otlp/otlptrace/otlptracehttp/client.go:230 - exporters/otlp/otlpmetric/otlpmetrichttp/client.go:170 - exporters/otlp/otlpmetric/otlpmetrichttp/client.go:201 - exporters/otlp/otlplog/otlploghttp/client.go:190 - exporters/otlp/otlplog/otlploghttp/client.go:221 permalinks (pinned): - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlptrace/otlptracehttp/client.go#L199 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlptrace/otlptracehttp/client.go#L230 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlpmetric/otlpmetrichttp/client.go#L170 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlpmetric/otlpmetrichttp/client.go#L201 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlplog/otlploghttp/client.go#L190 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlplog/otlploghttp/client.go#L221 root cause: each exporter client reads `resp.Body` using `io.Copy(&respData, resp.Body)` into a `bytes.Buffer` on both success and error paths, with no upper bound. impact: a malicious collector can force large transient heap allocations during export (peak memory scales with attacker-chosen response size) and can potentially crash the instrumented process (oom). affected component: - go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp - go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp - go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp repro (local-only): ```bash unzip poc.zip -d poc cd poc make canonical resp_bytes=33554432 chunk_delay_ms=0 ``` expected output contains: ``` [CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body) [PROOF_MARKER]: resp_bytes=33554432 peak_alloc_bytes=118050512 ``` control (same env, patched target): ```bash unzip poc.zip -d poc cd poc make control resp_bytes=33554432 chunk_delay_ms=0 ``` expected control output contains: ``` [CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body) [NC_MARKER]: resp_bytes=33554432 peak_alloc_bytes=512232 ``` attachments: poc.zip (attached) [PR_DESCRIPTION.md](https://github.com/user-attachments/files/25564272/PR_DESCRIPTION.md) [attack_scenario.md](https://github.com/user-attachments/files/25564273/attack_scenario.md) [poc.zip](https://github.com/user-attachments/files/25564271/poc.zip) Fixed in: https://github.com/open-telemetry/opentelemetry-go/pull/8108

Read the publisher's advisory

osv · GO-2026-4985

Published

The OTLP HTTP exporters (traces, metrics, and logs) do not limit the size of the HTTP response body read from the collector. A malicious or misconfigured collector can send a large response body, leading to excessive memory consumption and potential process termination (OOM).

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2026-39882

Published

OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Source published
8 Apr 2026 20:24:19 UTC
Source modified
9 Apr 2026 20:22:03 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 5.3 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2026-20628

Published

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory ex…

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Apr 8, 2026, 8:24:19 PM

dateUpdated: Apr 9, 2026, 8:22:03 PM

13 related source bulletins · separate from aliases

SUSE-SU-2026:3713-1: Security update for Multi-Linux Manager Client Tools - Monitoring stack

CVE-2025-12141 · CVE-2026-13149 · CVE-2026-33244 · CVE-2026-33382 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39882 · CVE-2026-41607

SUSE-SU-2026:4923-1: Security update for containerd

CVE-2026-39882 · CVE-2026-47262 · CVE-2026-53493 · CVE-2026-53495 · CVE-2026-95838

SUSE-SU-2026:3718-1: Security update for grafana

CVE-2025-12141 · CVE-2025-30153 · CVE-2026-21725 · CVE-2026-25680 · CVE-2026-25681 · CVE-2026-27136 · CVE-2026-28374 · CVE-2026-28376 · CVE-2026-28379 · CVE-2026-28380 · CVE-2026-28383 · CVE-2026-33376 · CVE-2026-33377 · CVE-2026-33378 · CVE-2026-33380 · CVE-2026-33381 · CVE-2026-33382 · CVE-2026-39821 · CVE-2026-39882 · CVE-2026-41607 · CVE-2026-42502 · CVE-2026-42506

RHSA-2026:37585: Red Hat Security Advisory: OpenShift Container Platform 4.22.5 bug fix and security update

CVE-2026-13676 · CVE-2026-33186 · CVE-2026-39882

SUSE-SU-2026:3714-1: Security update for Multi-Linux Manager Monitoring stack

CVE-2022-21698 · CVE-2025-12141 · CVE-2026-13149 · CVE-2026-33244 · CVE-2026-33382 · CVE-2026-33814 · CVE-2026-39821 · CVE-2026-39882 · CVE-2026-41607

openSUSE-SU-2026:22125-1: Security update for grafana

CVE-2026-1229 · CVE-2026-14199 · CVE-2026-17033 · CVE-2026-17183 · CVE-2026-19197 · CVE-2026-19475 · CVE-2026-21723 · CVE-2026-2303 · CVE-2026-33814 · CVE-2026-39882 · CVE-2026-41178 · CVE-2026-41606 · CVE-2026-42127 · CVE-2026-56852 · CVE-2026-73501 · CVE-2026-8609 · CVE-2026-9029

msrc_CVE-2026-39882: OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

CVE-2026-39882

WID-SEC-W-2026-2334: Red Hat OpenShift Container Platform (fast-uri,OpenTelemetry-Go) : Mehrere Schwachstellen

CVE-2026-13676 · CVE-2026-39882

openSUSE-SU-2026:11619-1: grafana-12.4.5-4.1 on GA media

CVE-2026-1229 · CVE-2026-21723 · CVE-2026-33814 · CVE-2026-39882 · CVE-2026-8609 · CVE-2026-9029

SUSE-SU-2026:4600-1: Security update for grafana, system-user-grafana

CVE-2026-1229 · CVE-2026-14199 · CVE-2026-17033 · CVE-2026-17183 · CVE-2026-19197 · CVE-2026-19475 · CVE-2026-21723 · CVE-2026-2303 · CVE-2026-33814 · CVE-2026-39882 · CVE-2026-41178 · CVE-2026-41606 · CVE-2026-42127 · CVE-2026-56852 · CVE-2026-73501 · CVE-2026-8595 · CVE-2026-8609 · CVE-2026-9029

RHSA-2026:54770: Red Hat Security Advisory: OpenShift Container Platform 4.22.10 bug fix and security update

CVE-2026-12143 · CVE-2026-14362 · CVE-2026-27136 · CVE-2026-39831 · CVE-2026-39882 · CVE-2026-42965 · CVE-2026-46597 · CVE-2026-50236 · CVE-2026-50237

SUSE-SU-2026:24381-1: Security update for containerd

CVE-2026-39882 · CVE-2026-47262 · CVE-2026-53488 · CVE-2026-53493 · CVE-2026-53495 · CVE-2026-95838

SUSE-SU-2026:4585-1: Security update 5.2.1 for Multi-Linux Manager Client Tools

CVE-2023-45289 · CVE-2024-22195 · CVE-2025-13836 · CVE-2025-4673 · CVE-2025-61686 · CVE-2026-0864 · CVE-2026-11940 · CVE-2026-11972 · CVE-2026-1229 · CVE-2026-13346 · CVE-2026-14199 · CVE-2026-1502 · CVE-2026-15308 · CVE-2026-1703 · CVE-2026-17033 · CVE-2026-17183 · CVE-2026-19197 · CVE-2026-19475 · CVE-2026-21723 · CVE-2026-2303 · CVE-2026-27459 · CVE-2026-3219 · CVE-2026-3276 · CVE-2026-33814 · CVE-2026-3446 · CVE-2026-3479 · CVE-2026-39821 · CVE-2026-39882 · CVE-2026-40181 · CVE-2026-40475 · CVE-2026-41066 · CVE-2026-41178 · CVE-2026-41606 · CVE-2026-42127 · CVE-2026-42211 · CVE-2026-42342 · CVE-2026-4360 · CVE-2026-44431 · CVE-2026-44990 · CVE-2026-45409 · CVE-2026-4786 · CVE-2026-49825 · CVE-2026-49853 · CVE-2026-49854 · CVE-2026-49855 · CVE-2026-53606 · CVE-2026-56852 · CVE-2026-6019 · CVE-2026-6100 · CVE-2026-6357 · CVE-2026-7210 · CVE-2026-73501 · CVE-2026-7774 · CVE-2026-8328 · CVE-2026-8595 · CVE-2026-8609 · CVE-2026-8643 · CVE-2026-9029

Source published
Apr 8, 2026, 8:24:19 PM (timezone not stated)
Source modified
Apr 9, 2026, 8:22:03 PM (timezone not stated)
Saved here
15 Nov 2026 11:06:47 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 5.3 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd · CVE-2026-39882

Published

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory ex…

OpenTelemetry-Go is the Go implementation of OpenTelemetry. Prior to 1.43.0, the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory bytes.Buffer without a size cap. This is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). This vulnerability is fixed in 1.43.0.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-789

Original publisher date fields

published: 2026-04-08T21:17:00.547

lastModified: 2026-07-24T21:10:00.143

1 source CPE criteria · context only
  • cpe:2.3:a:opentelemetry:opentelemetry:*:*:*:*:*:go:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
8 Apr 2026 21:17:00 UTC
Source modified
24 Jul 2026 21:10:00 UTC
Saved here
25 Oct 2026 09:17:24 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 5.3 CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

osv · GHSA-w8rr-5gcm-pp58

Published

opentelemetry-go: OTLP HTTP exporters read unbounded HTTP response bodies

overview: this report shows that the otlp HTTP exporters (traces/metrics/logs) read the full HTTP response body into an in-memory `bytes.Buffer` without a size cap. this is exploitable for memory exhaustion when the configured collector endpoint is attacker-controlled (or a network attacker can mitm the exporter connection). severity HIGH not claiming: this is a remote dos against every default deployment. claiming: if the exporter sends traces to an untrusted collector endpoint (or over a network segment where mitm is realistic), that endpoint can crash the process via a large response body. callsite (pinned): - exporters/otlp/otlptrace/otlptracehttp/client.go:199 - exporters/otlp/otlptrace/otlptracehttp/client.go:230 - exporters/otlp/otlpmetric/otlpmetrichttp/client.go:170 - exporters/otlp/otlpmetric/otlpmetrichttp/client.go:201 - exporters/otlp/otlplog/otlploghttp/client.go:190 - exporters/otlp/otlplog/otlploghttp/client.go:221 permalinks (pinned): - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlptrace/otlptracehttp/client.go#L199 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlptrace/otlptracehttp/client.go#L230 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlpmetric/otlpmetrichttp/client.go#L170 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlpmetric/otlpmetrichttp/client.go#L201 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlplog/otlploghttp/client.go#L190 - https://github.com/open-telemetry/opentelemetry-go/blob/248da958375e4dfb4a1105645107be3ef04b1c59/exporters/otlp/otlplog/otlploghttp/client.go#L221 root cause: each exporter client reads `resp.Body` using `io.Copy(&respData, resp.Body)` into a `bytes.Buffer` on both success and error paths, with no upper bound. impact: a malicious collector can force large transient heap allocations during export (peak memory scales with attacker-chosen response size) and can potentially crash the instrumented process (oom). affected component: - go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp - go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp - go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp repro (local-only): ```bash unzip poc.zip -d poc cd poc make canonical resp_bytes=33554432 chunk_delay_ms=0 ``` expected output contains: ``` [CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body) [PROOF_MARKER]: resp_bytes=33554432 peak_alloc_bytes=118050512 ``` control (same env, patched target): ```bash unzip poc.zip -d poc cd poc make control resp_bytes=33554432 chunk_delay_ms=0 ``` expected control output contains: ``` [CALLSITE_HIT]: otlptracehttp.UploadTraces::io.Copy(resp.Body) [NC_MARKER]: resp_bytes=33554432 peak_alloc_bytes=512232 ``` attachments: poc.zip (attached) [PR_DESCRIPTION.md](https://github.com/user-attachments/files/25564272/PR_DESCRIPTION.md) [attack_scenario.md](https://github.com/user-attachments/files/25564273/attack_scenario.md) [poc.zip](https://github.com/user-attachments/files/25564271/poc.zip) Fixed in: https://github.com/open-telemetry/opentelemetry-go/pull/8108

Source published
8 Apr 2026 19:22:01 UTC
Source modified
10 Sep 2026 03:51:03 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Publisher rating · MODERATE

osv · GO-2026-4985

Published

Oversized OTLP HTTP response bodies can cause memory exhaustion in go.opentelemetry.io/otel/exporters/otlp

The OTLP HTTP exporters (traces, metrics, and logs) do not limit the size of the HTTP response body read from the collector. A malicious or misconfigured collector can send a large response body, leading to excessive memory consumption and potential process termination (OOM).

Source published
26 May 2026 22:48:49 UTC
Source modified
27 May 2026 14:44:16 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 07:54 UTC · 270 of 275 readable · 255 fully read · 11 waiting for GitHub's hourly limit · documentation 469/469 current