Project Subscriptions
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-r6c9-g6q5-qrf9 | OpenTelemetry eBPF Instrumentation: CPU-mismatch fallback uses 256-byte buffer with 8KB size |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 03 Jun 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry ebpf Instrumentation
|
|
| CPEs | cpe:2.3:a:opentelemetry:ebpf_instrumentation:*:*:*:*:*:go:*:* | |
| Vendors & Products |
Opentelemetry ebpf Instrumentation
|
Tue, 02 Jun 2026 18:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 02 Jun 2026 17:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Opentelemetry
Opentelemetry opentelemetry-ebpf-instrumentation |
|
| Vendors & Products |
Opentelemetry
Opentelemetry opentelemetry-ebpf-instrumentation |
Tue, 02 Jun 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | OpenTelemetry eBPF Instrumentation: CPU-mismatch fallback uses 256-byte buffer with 8KB size | |
| Weaknesses | CWE-125 CWE-130 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-06-02T18:05:14.202Z
Reserved: 2026-05-12T21:59:25.667Z
Link: CVE-2026-45681
Updated: 2026-06-02T18:05:02.972Z
Status : Analyzed
Published: 2026-06-02T16:16:42.753
Modified: 2026-06-03T16:52:16.750
Link: CVE-2026-45681
No data.
OpenCVE Enrichment
Updated: 2026-06-02T17:15:18Z
Github GHSA