Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2026-39882

MEDIUM

CVE-2026-39882 is a medium-severity (CVSS 5.3) CWE-789 vulnerability in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. O3 Security confirms whether CVE-2026-39882 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenTelemetry-Go OTLP HTTP exporters read unbounded HTTP response bodies

Also known asGHSA-w8rr-5gcm-pp58GO-2026-4985
Published
Apr 8, 2026
Updated
Jul 31, 2026
Affected
3 pkgs
Patched
3 / 3
Exploits
None indexed

Blast Radius

3 pkgs affected
🐹go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp🐹go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp🐹go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogo.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttpall versions1.43.0
🐹Gogo.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttpall versions1.43.0
🐹Gogo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttpall versions0.19.0

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp to 1.43.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-39882 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-39882 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-39882. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2026-39882 in your dependencies?

O3 detects CVE-2026-39882 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.