CVE-2026-45681: open-telemetry opentelemetry-ebpf-instrumentation · Out-of-bounds Read
Affects open-telemetry opentelemetry-ebpf-instrumentationSource CVE Database V5
Not known to be exploited · CVSS 5.9 Medium : upgrade to 0.9.0 when convenient.
Data as of 29 Oct 2026, 19:04 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.9.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.
What to do
Upgrade opentelemetry-ebpf-instrumentation and open-telemetry/opentelemetry-ebpf-instrumentation to 0.9.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| open-telemetryopentelemetry-ebpf-instrumentation | Affected
| Fixed in
|
GitHubopen-telemetry/opentelemetry-ebpf-instrumentationpkg:github/open-telemetry/opentelemetry-ebpf-instrumentationOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade to open-telemetry opentelemetry-ebpf-instrumentation version 0.9.0 or later, where this vulnerability has been patched. No other mitigation or temporary workaround is indicated in the available data.
Description
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the per-CPU message-buffer fallback path uses a 256-byte backup buffer but preserves the original payload size, which can be up to 8KB. If a CPU mismatch occurs, OBI can read beyond the fallback buffer and leak adjacent memory into telemetry. This issue has been patched in version 0.9.0.