CVE-2026-9300
omec-project amf NGSetupRequest memory corruption
Description
A vulnerability has been found in omec-project amf up to 2.1.1. This affects an unknown part of the component NGSetupRequest Handler. Such manipulation leads to memory corruption. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. It is best practice to apply a patch to resolve this issue.
INFO
Published Date :
May 23, 2026, 11:45 a.m.
Last Modified :
May 23, 2026, 11:45 a.m.
Remotely Exploit :
No
Source :
VulDB
Affected Products
The following products are affected by CVE-2026-9300
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Update omec-project amf to the latest version.
- Apply the vendor-provided patch.
- Verify the patch installation.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-9300 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-9300 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by [email protected]
May. 23, 2026
Action Type Old Value New Value Added Description A vulnerability has been found in omec-project amf up to 2.1.1. This affects an unknown part of the component NGSetupRequest Handler. Such manipulation leads to memory corruption. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. It is best practice to apply a patch to resolve this issue. Added CVSS V4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L Added CVSS V2 (AV:N/AC:L/Au:S/C:P/I:P/A:P) Added CWE CWE-119 Added Reference https://github.com/omec-project/amf/ Added Reference https://github.com/omec-project/amf/issues/679 Added Reference https://github.com/omec-project/amf/pull/666 Added Reference https://vuldb.com/submit/811841 Added Reference https://vuldb.com/vuln/365247 Added Reference https://vuldb.com/vuln/365247/cti