ebpf-go is vulnerable to integer overflow via LoadCollectionSpecFromReader
CVE-2026-10722GHSA-xhgw-qwwf-pg32
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/cilium/ebpf 0.22.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 0.22.0
- Fixed in
- 0.22.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6238 lists affected ranges: Go github.com/cilium/ebpf >=0 <0.22.0 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-xhgw-qwwf-pg32 lists affected ranges: Go github.com/cilium/ebpf >=0 <0.22.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 1.9 · CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:P · score source
- EPSS
- CVE-2026-10722: 0.18% estimated exploitation activity in the next 30 days; percentile 7.49 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
A vulnerability has been found in cilium ebpf up to 0.21.0. This affects the function loadRawSpec of the file btf/btf.go of the component LoadCollectionSpec/LoadCollectionSpecFromReader. Such manipulation of the argument offset leads to integer overflow. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. The name of the patch is 533dfc82fd228bfadf42ea7180c39de7d9af47fa. A patch should be applied to remediate this issue.
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-xhgw-qwwf-pg32
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GO-2026-6238
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-10722 Advisory: ebpf-go is vulnerable to integer overflow via LoadCollectionSpecFromReader IDs: CVE-2026-10722, GHSA-xhgw-qwwf-pg32 Record: https://patchnext.com/advisories/cve-2026-10722 (revision 3, source checked 26 Oct 2026, 15:28 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Low (CVSS 1.9) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/cilium/ebpf 0.22.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/cilium/ebpf: affected < 0.22.0; fixed in 0.22.0 ## Suggested inspection (read-only) - Go github.com/cilium/ebpf: 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 github.com/cilium/ebpf. - 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://osv.dev/vulnerability/GO-2026-6238 (OSV record GO-2026-6238 lists affected ranges: Go github.com/cilium/ebpf >=0 <0.22.0 (fixed)) - Verified: https://github.com/advisories/GHSA-xhgw-qwwf-pg32 (GitHub-reviewed advisory GHSA-xhgw-qwwf-pg32 lists affected ranges: Go github.com/cilium/ebpf >=0 <0.22.0) Commands are suggestions: review each one before running it.
Loading voting…