Oversized OTLP HTTP response bodies can cause memory exhaustion in go.opentelemetry.io/otel/exporters/otlp
Published 26 May 2026 · Updated 27 May 2026
Is your project on an affected go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected packages
- Affected
- <0.19.0
- Fixed in
- 0.19.0
go get go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp@v0.19.0- Affected
- <1.43.0
- Fixed in
- 1.43.0
go get go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp@v1.43.0- Affected
- <1.43.0
- Fixed in
- 1.43.0
go get go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp@v1.43.0Details
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).
Is GO-2026-4985 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.