CVE-2026-8782: omec-project amf · NULL Pointer Dereference
Affects omec-project amfSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 07:57 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 22% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 18 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| omec-projectamf | Affected
| Fixed in– |
GitHubomec-project/amfpkg:github/omec-project/amfOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:omec-project:amf:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade the omec-project amf component to version 2.2.0 or later, as this version contains the fix for the null pointer dereference vulnerability. No other mitigation or temporary workaround is indicated. Patch status is confirmed by the vendor recommendation to upgrade.
Description
CVE-2026-8782 is a medium severity vulnerability in the omec-project amf component up to version 2.1.3-dev. It involves a null pointer dereference in the NGAP Message Handler, specifically in the file ngap/handler.go. This flaw can be remotely exploited without user interaction or privileges. Public exploit code is available. Upgrading to version 2.2.0 mitigates the issue as the fix is included in that release.
References
- vuldb.com/vuln/364406 (opens in a new tab)
- vuldb.com/vuln/364406/cti (opens in a new tab)
- vuldb.com/submit/811654 (opens in a new tab)
- github.com/omec-project/amf/issues/674 (opens in a new tab)
- github.com/omec-project/amf/pull/666 (opens in a new tab)
- github.com/omec-project/amf/releases/tag/v2.2.0 (opens in a new tab)
- github.com/omec-project/amf/ (opens in a new tab)