CVE-2026-120859PyMoDAQ eval injection
CVE-2026-120859 is a eval injection in PyMoDAQ, rated high (8.5 on CVSS 4.0).
Why this priority: High severity, with no exploitation signal yet.
Published · Updated · NVD status: Received
What it is
Input reaches an eval-style call and runs as code. Serialized objects from outside are turned back into live objects, which a crafted payload can abuse to run code.
How it is reached
An attacker can exploit it by someone who can already run code or sign in on the machine, without an account, but someone has to act first, such as opening a file or following a link.
What an attacker gains
A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker run commands or code with the privileges of the affected service.
Is it being exploited?
CISA's SSVC assessment notes a public proof of concept. EPSS estimates a 0.19% chance of exploitation activity in the next 30 days, higher than 9% of scored CVEs.
What to do
- Apply the update for your edition of PyMoDAQ. Fixed builds: PyMoDAQ: 4.4.13; pymodaq_data: 5.1.15, 5.2.14, 5.3.10; pymodaq_gui: 5.1.15, 5.2.14, 5.3.10; pymodaq_utils: 5.1.15, 5.2.14, 5.3.10.
- Limit who can run code or sign in on the hosts that run it.
- Warn the people who use it, and filter files and links on the way in.
Description from NVD
PyMoDAQ before 4.4.13, and pymodaq_data, pymodaq_gui, and pymodaq_utils before 5.1.15, 5.2.x before 5.2.14, and 5.3.x before 5.3.10, contain deserialization of untrusted data and eval injection vulnerabilities that allow attackers to execute arbitrary code by supplying crafted files that a user opens. Attackers can store pickled objects in HDF5 string nodes that StringARRAY.array_to_string() passes to pickle.loads() when the node is browsed or read, place Python expressions in HDF5 attributes that JsonConverter.json2object() evaluates, supply a .dock file that load_layout_state() unpickles from the Dashboard Load layout action, or embed Python expressions in XML settings files that elt_to_dict() and set_txt_from_elt() evaluate.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- Application servers and the hosts they run on. The flaw sits between untrusted input and code or command execution.
- Template engines. The flaw sits between untrusted input and code or command execution.
- APIs, queues and caches that accept serialized objects. The flaw sits between a message producer and the service that deserializes it.
Trust boundaries in play
- Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
- People who open files and links. Mail, chat and browsers are the delivery path.
- Between untrusted input and code or command execution. An attacker who crosses it can run commands or code with the privileges of the affected service.
- Between a message producer and the service that deserializes it. An attacker who crosses it can turn crafted data into code execution inside the receiving service.
Questions to answer about your own systems
- Where does PyMoDAQ run in your systems, and at which version?
- Which of those hosts also run code or users you do not fully trust?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Patches and commits
Advisories
Releases
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.