go.opentelemetry.io/ebpf-profiler

CVE-2026-48496

CVE-2026-48496 is a medium-severity allocation of resources without limits or throttling vulnerability in go.opentelemetry.io/ebpf-profiler (go), affecting versions >= 0.0.202527, < 0.0.202622. It is fixed in 0.0.202622.

Key facts
CVSS score
6.2
Medium
Attack vector
Local
Issuing authority
GitHub Advisory Database
Affected package
go.opentelemetry.io/ebpf-profiler
Fixed in
0.0.202622
Disclosed
2026

Summary

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.

Impact

What is allocation of resources without limits or throttling?

The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap. Typical impact: resource exhaustion leading to denial of service.

Severity and exposure

CVE-2026-48496 has a CVSS score of 6.2 (Medium). The vector is requires local access, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (0.0.202622). Upgrading removes the vulnerable code path.

Affected versions

go

  • go.opentelemetry.io/ebpf-profiler (>= 0.0.202527, < 0.0.202622)

Security releases

  • go.opentelemetry.io/ebpf-profiler → 0.0.202622 (go)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-48496 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-48496 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-48496 in your environment

Remediation advice

Upgrade go.opentelemetry.io/ebpf-profiler to 0.0.202622 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-48496

What is CVE-2026-48496?

CVE-2026-48496 is a medium-severity allocation of resources without limits or throttling vulnerability in go.opentelemetry.io/ebpf-profiler (go), affecting versions >= 0.0.202527, < 0.0.202622. It is fixed in 0.0.202622. The application allocates resources such as memory, threads, or file descriptors based on untrusted input without enforcing a cap.

How severe is CVE-2026-48496?

CVE-2026-48496 has a CVSS score of 6.2 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of go.opentelemetry.io/ebpf-profiler are affected by CVE-2026-48496?

go.opentelemetry.io/ebpf-profiler (go) versions >= 0.0.202527, < 0.0.202622 is affected.

Is there a fix for CVE-2026-48496?

Yes. CVE-2026-48496 is fixed in 0.0.202622. Upgrade to this version or later.

Is CVE-2026-48496 exploitable, and should I be worried?

Whether CVE-2026-48496 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-48496 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-48496?

Upgrade go.opentelemetry.io/ebpf-profiler to 0.0.202622 or later.

Stop the waste.
Protect your environment with Kodem.