Skip to content

Update module go.opentelemetry.io/ebpf-profiler to v0.0.202622 [SECURITY] - #574

Merged
renovate-update-app[bot] merged 1 commit into
stackstate-7.78.2from
renovate/go-go.opentelemetry.io-ebpf-profiler-vulnerability
Oct 28, 2026
Merged

renovate-update-app[bot] merged 1 commit into
stackstate-7.78.2from
renovate/go-go.opentelemetry.io-ebpf-profiler-vulnerability

Conversation

@renovate-update-app

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/ebpf-profiler v0.0.202547 → v0.0.202622 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


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

CVE-2026-48496 / GHSA-f2r5-5m7w-p5cx / GO-2026-5343

More information

Details

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 open-telemetry/opentelemetry-ebpf-profiler@234b685.

Fix is part of v.0.0.202622.

Severity

  • CVSS Score: 6.2 / 10 (Medium)
  • Vector String: CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

This data is provided by OSV and the GitHub Advisory Database (CC-BY 4.0).


opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler agent in go.opentelemetry.io/ebpf-profiler

CVE-2026-48496 / GHSA-f2r5-5m7w-p5cx / GO-2026-5343

More information

Details

opentelemetry-ebpf-profiler: Unprivileged process can trigger a denial of service on the ebpf-profiler agent in go.opentelemetry.io/ebpf-profiler

Severity

Unknown

References

This data is provided by OSV and the Go Vulnerability Database (CC-BY 4.0).


Release Notes

open-telemetry/opentelemetry-ebpf-profiler (go.opentelemetry.io/ebpf-profiler)

v0.0.202622

Compare Source

v0.0.202618

Compare Source

v0.0.202614

Compare Source

v0.0.202613

Compare Source

v0.0.202610

Compare Source

v0.0.202606

Compare Source

v0.0.202601

Compare Source

v0.0.202549

Compare Source


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate CLI.

@renovatee-approver-stackvista renovatee-approver-stackvista Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Auto-approving verified Renovate commits with native automerge enabled.

@renovate-update-app
renovate-update-app Bot force-pushed the renovate/go-go.opentelemetry.io-ebpf-profiler-vulnerability branch 3 times, most recently from b5b717d to 6c44682 Compare October 26, 2026 08:44
@renovate-update-app
renovate-update-app Bot force-pushed the renovate/go-go.opentelemetry.io-ebpf-profiler-vulnerability branch from 6c44682 to bff12a0 Compare October 28, 2026 01:36
@renovate-update-app
renovate-update-app Bot added this pull request to the merge queue Oct 28, 2026
Merged via the queue into stackstate-7.78.2 with commit 7352919 Oct 28, 2026
42 checks passed
@renovate-update-app
renovate-update-app Bot deleted the renovate/go-go.opentelemetry.io-ebpf-profiler-vulnerability branch October 28, 2026 04:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants