Skip to content
Fencer Intel
medium 5.1

CVE-2026-45682 json

OpenTelemetry eBPF Instrumentation: CappedConcurrentHashMap leaks keys after removals

published 5mo ago modified 3mo ago also EUVD-2026-33950 , GHSA-962q-hwm5-52x5 , GO-2026-5275

cvss
5.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.2%
EPSS 0.2% chance of exploitation in 30 days, percentile 5%
public exploits
0
none known

Summary

OpenTelemetry eBPF Instrumentation provides eBPF instrumentation based on the OpenTelemetry standard. Prior to version 0.9.0, the custom CappedConcurrentHashMap introduced for Java TLS state tracking never removes keys from its insertion-order queue when entries are deleted. In long-running instrumented JVMs, repeated connection churn can therefore grow the queue without bound and exhaust heap memory. 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 SLE Module for Basesystem 15 SP7 1.17.1-150700.15.23.1
  • alloy SLES for SAP applications 16.0, SLES 16.0 1.17.0-160000.1.1

suse advisories SUSE-SU-2026:2824-1SUSE-SU-2026:22575-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
  • alloy openSUSE Leap 16.0 1.17.0-160000.1.1
  • alloy openSUSE Tumbleweed 1.17.0-1.1

opensuse advisories openSUSE-SU-2026:21483-1openSUSE-SU-2026:21251-1openSUSE-SU-2026:11053-1

Is CVE-2026-45682 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
5mo ago

Exploit prediction

0.16% chance of exploitation in the next 30 days, higher than 5% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • github.com https://github.com/open-telemetry/opentelemetry-ebpf-instrumentation/security/advisories/GHSA-962q-hwm5-52x5 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 5.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 5.5 CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

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

Weakness
  • CWE-401 Missing Release of Memory after Effective Lifetime
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel 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.