CVE-2026-45683: OpenTelemetry OBI kernel memory disclosure in Java TLS ioctl probe

CVE-2026-45683 · Severity: low · CVSS 3.8 · Published 2026-06-02

OpenTelemetry eBPF Instrumentation is a tool used to monitor application performance and network traffic at a deep system level. A security flaw in its Java TLS monitoring component allows a local user or process to trick the tool into reading sensitive data from the operating system's kernel memory. This could result in the accidental exposure of private system information through the tool's normal monitoring reports (telemetry).

Technologies: go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation, Opentelemetry Otelhttp. Vendors: Go, Opentelemetry.

Quick answers

Is CVE-2026-45683 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-45683 being exploited in the wild.
How severe is CVE-2026-45683?
Low severity, with a CVSS score of 3.8, published 2 June 2026.
Which products and versions are affected?
go.opentelemetry.io/obi (Go) < 0.9.0, SEMVER:introduced=0,fixed=0.9.0; Opentelemetry Ebpf Instrumentation Prior to 0.9.0.
Is there a fix for CVE-2026-45683?
Yes. go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-45683 attacked?
It is attacked with local access, in a software library.
Am I affected by CVE-2026-45683?
Check whether you run go.opentelemetry.io/obi (Go), Opentelemetry Ebpf Instrumentation or Opentelemetry Otelhttp at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • go.opentelemetry.io/obi (Go): upgrade to 0.9.0 or later
    go get go.opentelemetry.io/obi@v0.9.0

Technical details

A vulnerability exists in the Java TLS ioctl kprobe within OpenTelemetry eBPF Instrumentation (OBI) prior to version 0.9.0. The probe, located in 'bpf/generictracer/java_tls.c', incorrectly uses 'bpf_probe_read' instead of 'bpf_probe_read_user' when processing user-controlled ioctl pointers. Because the third argument of the ioctl is treated as a structured buffer without proper memory space validation, a local instrumented process can supply a kernel-space pointer. This allows an attacker to bypass security boundaries and cause the BPF program to copy kernel memory into the telemetry ring buffer, leading to information disclosure. The issue is patched in version 0.9.0.

Affected products

  • OpenTelemetry OpenTelemetry eBPF Instrumentation (OBI) Prior to 0.9.0

Identifiers

  • CVE-2026-45683
  • GHSA-fjq3-ffvr-vm46
  • GO-2026-5366

Timeline

  • 2026-05-11: patched: Version 0.9.0 released
  • 2026-05-12: advisory: GitHub Security Advisory GHSA-fjq3-ffvr-vm46 published
  • 2026-06-02: disclosed: CVE-2026-45683 published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.