CVE-2026-8780: omec-project amf · Memory Corruption
Affects omec-project amfSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 19 Nov 2026, 20:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 23% 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
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| omec-projectamf | Affected
| Fixed in– |
Gogithub.com/omec-project/amfpkg:golang/github.com/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 official fix for this vulnerability along with other security issues. No other specific mitigations are indicated. Patch status is confirmed by the vendor's advisory information.
Description
A vulnerability was identified in omec-project amf up to 2.1.3-dev. The affected element is an unknown function of the file ngap/dispatcher.go of the component NGAP Message Handler. The manipulation leads to memory corruption. The attack may be initiated remotely. The exploit is publicly available and might be used. Upgrading to version 2.2.0 is sufficient to fix this issue. It is suggested to upgrade the affected component. The same pull request fixes multiple security issues.
References
- vuldb.com/vuln/364404 (opens in a new tab)
- vuldb.com/vuln/364404/cti (opens in a new tab)
- vuldb.com/submit/811617 (opens in a new tab)
- github.com/omec-project/amf/issues/670 (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)