CVE-2026-45681 json
OpenTelemetry eBPF Instrumentation: CPU-mismatch fallback uses 256-byte buffer with 8KB size
published 2026-05-18 5 mo ago modified 2026-07-22 3 mo ago also EUVD-2026-33955 , GHSA-r6c9-g6q5-qrf9 , GO-2026-5610
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 21%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go go.opentelemetry.io/obi 0.9.0
- opentelemetry ebpf_instrumentation 0.9.0
- opentelemetry opentelemetry_ebpf_instrumentation 0.9.0
- alloy SLES for SAP applications 16.0, SLES 16.0 1.19.2-160000.1.1
- alloy SLE Module for Basesystem 15 SP7 1.19.2-150700.15.29.1
suse advisories SUSE-SU-2026:24148-1SUSE-SU-2026:4408-1
- alloy openSUSE Leap 16.0 1.19.2-160000.1.1
- alloy openSUSE Tumbleweed 1.19.2-1.1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:22032-1openSUSE-SU-2026:11803-1openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.29% chance of exploitation in the next 30 days, higher than 21% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-r6c9-g6q5-qrf9 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
| GitHub | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | go.opentelemetry.io/obi | <0.9.0 |
0.9.0 |
Affected products
- open-telemetry opentelemetry-ebpf-instrumentation
Classification
References
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-r6c9-g6q5-qrf9
exploit, web, vendor-advisory, advisory
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation/releases/tag/v0.9.0
web, product, release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-45681
advisory
-
github.com
/open-telemetry/opentelemetry-ebpf-instrumentation
package
Sources
- CVE List CVE-2026-45681
- GitHub Advisory GHSA-r6c9-g6q5-qrf9
- NVD CVE-2026-45681
- OSV GO-2026-5610
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.