Advisory record · GHSA-962q-hwm5-52x5

OpenTelemetry eBPF Instrumentation: CappedConcurrentHashMap leaks keys after removals

CVSS 5.1 MediumEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 18 May 2026, 20:17 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
go.opentelemetry.io/obiGo<0.9.00.9.0
Identifiers
GHSA-962q-hwm5-52x5 · CVE-2026-45682 · GO-2026-5275
Weakness (CWE)
CWE-401 · CWE-770
Published
18 May 2026
Updated
25 Jun 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Go package go.opentelemetry.io/obi versions before 0.9.0 are affected. The Java TLS instrumentation's CappedConcurrentHashMap never removes deleted keys from its insertion-order queue, so a JVM with ongoing connection churn can grow that queue until heap is exhausted and the instrumented Java workload fails with OutOfMemoryError. Upgrade to 0.9.0 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.1 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:07 UTC First seen by agentprime
  2. 31 Oct 2026, 15:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.