Is CVE-2026-45682 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-45682 being exploited in the wild.

How severe is CVE-2026-45682?

Medium severity, with a CVSS score of 5.1, 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 < 0.9.0, Prior to 0.9.0.

Is there a fix for CVE-2026-45682?

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-45682 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-45682?

Check whether you run go.opentelemetry.io/obi (Go) or Opentelemetry Ebpf Instrumentation 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.

CVE-2026-45682: OpenTelemetry eBPF Instrumentation memory leak in Java TLS tracking

Q: Is there a fix for CVE-2026-45682?

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.

Q: How is CVE-2026-45682 attacked?

It is attacked with local access, in a software library.

Q: Am I affected by CVE-2026-45682?

Check whether you run go.opentelemetry.io/obi (Go) or Opentelemetry Ebpf Instrumentation 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.

CVE-2026-45682 · Severity: medium · CVSS 5.1 · Published 2026-06-02

OpenTelemetry eBPF Instrumentation is a tool used to monitor application performance and security. A flaw in how it tracks Java encrypted (TLS) connections causes it to leak memory every time a connection is opened and closed. Over time, this can lead to system instability, significant performance slowdowns, or complete application crashes due to memory exhaustion.

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

Quick answers

Is CVE-2026-45682 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-45682 being exploited in the wild.
How severe is CVE-2026-45682?: Medium severity, with a CVSS score of 5.1, 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 < 0.9.0, Prior to 0.9.0.
Is there a fix for CVE-2026-45682?: 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-45682 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-45682?: Check whether you run go.opentelemetry.io/obi (Go) or Opentelemetry Ebpf Instrumentation 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 memory leak exists in the custom CappedConcurrentHashMap implementation used for Java TLS state tracking in OpenTelemetry eBPF Instrumentation (OBI). While the map correctly limits its size during 'put' operations, the 'remove' method fails to remove keys from the internal ConcurrentLinkedQueue used for tracking insertion order. In environments with high connection churn, this queue grows indefinitely even if the active map size remains small. An attacker or high-traffic workload can trigger repeated TLS handshakes to exhaust the JVM heap, leading to OutOfMemoryError (OOM) and denial of service. This issue is addressed in version 0.9.0 by replacing the leaky map with a ring-buffer-backed implementation.

Affected products

OpenTelemetry OpenTelemetry eBPF Instrumentation (OBI) Prior to 0.9.0

Identifiers

CVE-2026-45682
GHSA-962q-hwm5-52x5
GO-2026-5275

Timeline

2026-05-11: patched: Version 0.9.0 released
2026-05-12: advisory: GitHub Security Advisory published
2026-06-02: disclosed: CVE published to NVD

References

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