← Back
CVE-2026-48496
Vulnerability in go.opentelemetry.io/ebpf-profiler (CVE-2026-48496)
Summary
vulnerability in go.opentelemetry.io/ebpf-profiler (CVE-2026-48496). Risk of unauthorized operations or information disclosure. Exploitable via ``processPIDEvents``. Mitigation: upgrade to `0.0.202622` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-48496** has been found in go.opentelemetry.io/ebpf-profiler.
Attackers can target a specific entry point like ``processPIDEvents`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade go.opentelemetry.io/ebpf-profiler to **0.0.202622** or later.
If unsure, ask your IT team or search "go.opentelemetry.io/ebpf-profiler CVE-2026-48496" on the vendor's site.
CVE-2026-48496 (go.opentelemetry.io/ebpf-profiler) — CWE-770 /
Attack surface: `processPIDEvents` / `openat2`
Patched: `0.0.202622` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**A vulnerability** (CWE-770) exists in go.opentelemetry.io/ebpf-profiler. Attackers reach the vulnerable code path via ``processPIDEvents`` without authentication.
📍 Affected scope
go.opentelemetry.io/ebpf-profiler — . Attack surface: `processPIDEvents` / `openat2`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **0.0.202622**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'go.opentelemetry.io/ebpf-profiler' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'go.opentelemetry.io/ebpf-profiler' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `go.opentelemetry.io/ebpf-profiler` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade go.opentelemetry.io/ebpf-profiler to 0.0.202622ステージング環境で 0.0.202622 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
go
go.opentelemetry.io/ebpf-profiler
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.0.202622"}]}]
References
- web https://github.com/open-telemetry/opentelemetry-ebpf-profiler/security/advisories/GHSA-f2r5-5m7w-p5cx
- web https://github.com/open-telemetry/opentelemetry-ebpf-profiler/commit/234b685cab31c2cb2f79e966caeab168bcc489e4
- web https://github.com/open-telemetry/opentelemetry-ebpf-profiler/releases/tag/v0.0.202622
- web https://github.com/advisories/GHSA-f2r5-5m7w-p5cx