opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler agent

Exploitation

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

CVSS

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

EPSS

• CVE-2026-48496: 0.14% estimated exploitation activity in the next 30 days; percentile 3.13 (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 An unprivileged process can easily trigger the processPIDEvents goroutine to be blocked indefinitely, preventing the goroutine from analyzing any new ELF file. The goroutine stays blocked in the openat2 syscall forever and the profiler can no longer work properly, it is a denial of service. Impact The impact is limited to denial-of-service on the ebpf-profiler agent: - There has to be a malicious workload albeit unprivileged. - No exfiltration of data. No loss of data. Fix Fixed in https://github.com/open-telemetry/opentelemetry-ebpf-profiler/commit/234b685cab31c2cb2f79e966caeab168bcc489e4. Fix is part of v.0.0.202622.

Published by the source

23 Jun 2026, 22:16 UTC

Last modified by the source

23 Jun 2026, 22:16 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-f2r5-5m7w-p5cx

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

# Patch Next advisory brief: CVE-2026-48496

Advisory: opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler agent
IDs: CVE-2026-48496, GHSA-f2r5-5m7w-p5cx
Record: https://patchnext.com/advisories/cve-2026-48496 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.2)
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/ebpf-profiler 0.0.202622. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go go.opentelemetry.io/ebpf-profiler: affected >= 0.0.202527, < 0.0.202622; fixed in 0.0.202622

## Suggested inspection (read-only)
- Go go.opentelemetry.io/ebpf-profiler: 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/ebpf-profiler.
- 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-f2r5-5m7w-p5cx (GitHub-reviewed advisory GHSA-f2r5-5m7w-p5cx lists affected ranges: Go go.opentelemetry.io/ebpf-profiler >=0.0.202527 <0.0.202622)

Commands are suggestions: review each one before running it.