OpenTelemetry eBPF Instrumentation: Unbounded BPF internal metrics replay can exhaust CPU
Published 18 May 2026 · Updated 25 Jun 2026
Is your project on an affected go.opentelemetry.io/obi?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <0.9.0
- Fixed in
- 0.9.0
go get go.opentelemetry.io/obi@v0.9.0Details
Summary
OBI replays BPF probe hits into histogram observations by looping once per recorded run count. On busy systems, the run-count delta can become very large, causing the metrics exporter to spend excessive CPU time in a tight loop every collection interval.
Details
The vulnerable loop is in pkg/export/prom/prom_bpf.go. During each metrics tick, OBI iterates through probeMetrics and then executes for range metric.count, invoking BpfProbeLatency(...) for each individual recorded hit.
The count comes from `calculateStats()` in the same file, where deltaCount := bp.runCount - bp.prevRunCount is calculated and returned without any cap before the per-hit replay loop.
If probe activity spikes between scrape intervals, deltaCount can be very large. The exporter then spends CPU time proportional to the number of probe hits rather than the number of metric series.
PoC
Local testing with a small reproducer confirmed the replay-loop behavior and showed CPU scaling with the recorded hit count rather than the number of metric series.
Use a vulnerable build and enable internal metrics export:
git checkout v0.0.0-rc.1+build make build export OTEL_EBPF_INTERNAL_METRICS_PROMETHEUS_PORT=9090 sudo ./bin/obi
Create a high-rate workload that repeatedly exercises traced probes. For example, generate HTTP traffic against an instrumented service:
python3 -m http.server 18081
Then drive it:
seq 1 500000 | xargs -P 128 -I{} curl -s http://127.0.0.1:18081 >/dev/nullAt the same time, scrape metrics repeatedly:
while true; do curl -s http://127.0.0.1:9090/metrics >/dev/null; done
On a vulnerable build, OBI CPU consumption rises sharply during the metrics loop because histogram updates are replayed once per counted probe execution. The effect is visible in top or pidstat and is most pronounced under sustained high request volume.
Impact
This is an availability issue in the internal metrics path. Any deployment that enables BPF internal metrics and traces busy workloads is affected. Attackers can indirectly consume CPU in the privileged agent by driving enough activity through instrumented services.
Is GHSA-89c6-vpcj-7vj4 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/obi, and gives you the command that fixes it.
More advisories for go.opentelemetry.io/obi
- LowCVE-2026-45684OpenTelemetry eBPF Instrumentation: Log enricher writev path can overread and overwrite user buffers in go.opentelemetry.io/obi · 25 Jun 2026
- LowCVE-2026-45676OpenTelemetry eBPF Instrumentation: Unsafe fastelf parsing allows malformed ELF to crash agent in go.opentelemetry.io/obi · 25 Jun 2026
- LowCVE-2026-45678OpenTelemetry eBPF Instrumentation: Postgres BIND parsing can panic on malformed payloads in go.opentelemetry.io/obi · 25 Jun 2026
- LowCVE-2026-45681OpenTelemetry eBPF Instrumentation: CPU-mismatch fallback uses 256-byte buffer with 8KB size in go.opentelemetry.io/obi · 25 Jun 2026
- LowCVE-2026-45685OpenTelemetry eBPF Instrumentation: MongoDB parser panics on malformed wire messages in go.opentelemetry.io/obi · 25 Jun 2026
- LowCVE-2026-45683OpenTelemetry eBPF Instrumentation: Java TLS ioctl kprobe allows kernel memory disclosure in go.opentelemetry.io/obi · 25 Jun 2026
References
- Linkgithub.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-89c6-vpcj-7vj4
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-45680
- Packagegithub.com/open-telemetry/opentelemetry-ebpf-instrumentation
- Linkgithub.com/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.9.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.