CVE-2026-8349: omec-project amf · Memory Corruption
Affects omec-project amfSource CVE Database V5
Public exploit available · CVSS 5.3 Medium.
Data as of 30 Oct 2026, 11:52 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 11 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 30 Oct 2026.
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– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch has been published to fix this vulnerability (commit 8a4c33cdda866094f1989bdeff6d8642fce8de8435f89defd66831c97715f5aa). It is recommended to apply this patch promptly to remediate the issue. Since the product is not a cloud service, remediation depends on the user applying the patch. Patch status is confirmed by the presence of the patch commit identifier.
Description
CVE-2026-8349 is a medium-severity vulnerability in the omec-project amf component, specifically in the NGAP Message Handler. It allows remote attackers with low privileges to cause memory corruption by manipulating the affected component. The vulnerability affects versions 2.1.0 and 2.1.1 of the product. A patch identified by commit 8a4c33cdda866094f1989bdeff6d8642fce8de8435f89defd66831c97715f5aa has been released to address this issue. There are no known exploits in the wild at this time.
References
- vuldb.com/vuln/362663 (opens in a new tab)
- vuldb.com/vuln/362663/cti (opens in a new tab)
- vuldb.com/submit/811475 (opens in a new tab)
- github.com/omec-project/amf/issues/672 (opens in a new tab)
- github.com/omec-project/amf/pull/666 (opens in a new tab)
- hub.docker.com/layers/omecproject/5gc-amf/rel-2.2.1/images/sha256-8a4c33cdda866094f1989bdeff6d8642fce8de8435f89defd66831c97715f5aa (opens in a new tab)
- github.com/omec-project/amf/ (opens in a new tab)