opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler agentGHSA-f2r5-5m7w-p5cx
MEDIUMFix: open-telemetry/opentelemetry-ebpf-profiler@234b685GHSA-f2r5-5m7w-p5cx is a medium-severity (CVSS 6.2) CWE-770 vulnerability in go.opentelemetry.io/ebpf-profiler. A fix is available for go.opentelemetry.io/ebpf-profiler — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f2r5-5m7w-p5cx.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
go.opentelemetry.io/ebpf-profilerReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
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
Fix is part of v.0.0.202622.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | go.opentelemetry.io/ebpf-profiler | ≥ 0.0.202527&&< 0.0.202622 | 0.0.202622go get go.opentelemetry.io/ebpf-profiler@v0.0.202622 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for go.opentelemetry.io/ebpf-profiler, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update go.opentelemetry.io/ebpf-profiler to 0.0.202622 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f2r5-5m7w-p5cx is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.
Frequently Asked Questions
Is GHSA-f2r5-5m7w-p5cx in your dependencies?
Find it across Go, including transitive dependencies.