CVE-2026-45678: open-telemetry opentelemetry-ebpf-instrumentation · Improper Input Validation
Affects open-telemetry opentelemetry-ebpf-instrumentationSource CVE Database V5
Not known to be exploited · CVSS 7.5 High : upgrade to 0.9.0 soon.
Data as of 30 Oct 2026, 06:59 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% 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:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation 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 OpenTelemetry eBPF Instrumentation to version 0.9.0 or later, where this vulnerability is patched. Since the vendor advisory indicates the issue is fixed in 0.9.0, applying this official fix fully mitigates the vulnerability. No other mitigation steps are specified.
Description
OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the Postgres protocol parser assumes BIND message payloads contain a valid NUL-terminated portal name. A crafted empty or unterminated payload can make OBI slice beyond the end of the captured buffer and panic. This issue has been patched in version 0.9.0.