OpenTelemetry eBPF Instrumentation: CappedConcurrentHashMap leaks keys after removals

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.1 · CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2026-45682: 0.16% estimated exploitation activity in the next 30 days; percentile 5.37 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details The vulnerable implementation is in pkg/internal/java/agent/src/main/java/io/opentelemetry/obi/java/instrumentations/util/CappedConcurrentHashMap.java#L11. New keys are appended to a ConcurrentLinkedQueue, and eviction only runs inside put() when map.size() capacity. The remove() method removes the key from the ConcurrentHashMap but leaves the key in the queue. Because evictIfNeeded() only checks map.size() capacity, the queue can grow forever in workloads that insert and remove keys while keeping the live map below the cap. This pattern is reachable from pkg/internal/java/agent/src/main/java/io/opentelemetry/obi/java/instrumentations/data/SSLStorage.java#L66, where cleanupConnectionBufMapping…

Published by the source

18 May 2026, 20:17 UTC

Last modified by the source

9 Jun 2026, 10:58 UTC

Source last checked

26 Oct 2026, 15:23 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-962q-hwm5-52x5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-45682

Advisory: OpenTelemetry eBPF Instrumentation: CappedConcurrentHashMap leaks keys after removals
IDs: CVE-2026-45682, GHSA-962q-hwm5-52x5
Record: https://patchnext.com/advisories/cve-2026-45682 (revision 1, source checked 26 Oct 2026, 15:23 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: go.opentelemetry.io/obi 0.9.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/obi: affected < 0.9.0; fixed in 0.9.0

## Suggested inspection (read-only)
- Go go.opentelemetry.io/obi: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on go.opentelemetry.io/obi.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-962q-hwm5-52x5 (GitHub-reviewed advisory GHSA-962q-hwm5-52x5 lists affected ranges: Go go.opentelemetry.io/obi >=0 <0.9.0)

Commands are suggestions: review each one before running it.