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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-39882: 0.19% estimated exploitation activity in the next 30 days; percentile 8.74 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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): -…

Published by the source

8 Apr 2026, 19:22 UTC

Last modified by the source

9 Apr 2026, 14:29 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-w8rr-5gcm-pp58

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-39882

Advisory: opentelemetry-go: OTLP HTTP exporters read unbounded HTTP response bodies
IDs: CVE-2026-39882, GHSA-w8rr-5gcm-pp58
Record: https://patchnext.com/advisories/cve-2026-39882 (revision 1, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp 1.43.0; go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp 0.19.0; go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp 1.43.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp: affected < 1.43.0; fixed in 1.43.0
- Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp: affected < 0.19.0; fixed in 0.19.0
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp: affected < 1.43.0; fixed in 1.43.0

## Suggested inspection (read-only)
- Go go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp: check the installed version with your package manager.
- Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp, go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp, go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w8rr-5gcm-pp58 (GitHub-reviewed advisory GHSA-w8rr-5gcm-pp58 lists affected ranges: Go go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp >=0 =0 =0 <0.19.0)

Commands are suggestions: review each one before running it.