# CVE-2026-120859: PyMoDAQ before 5.3.10 Arbitrary Code Execution via Crafted HDF5, Dock Layout, and XML Settings Files


- **Severity:** High 8.5 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-jw9g-5c9x-cf84

## What is CVE-2026-120859?

CVE-2026-120859 is a high-severity vulnerability in PyMoDAQ, published on 5 Nov 2026. 

### Official description

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.

Weakness: CWE-95 (Improper Neutralization of Directives in Dynamically Evaluated Code), CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-120859?

10 open source packages ship an affected version, including pymodaq-data, pymodaq and pymodaq-gui.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `pymodaq-data` | PyPI | `pkg:pypi/pymodaq-data` | All versions | 5.1.15 |
| `pymodaq-data` | PyPI | `pkg:pypi/pymodaq-data` | From 5.2.0 | 5.2.14 |
| `pymodaq-data` | PyPI | `pkg:pypi/pymodaq-data` | From 5.3.0 | 5.3.10 |
| `pymodaq` | PyPI | `pkg:pypi/pymodaq` | All versions | 4.4.13 |
| `pymodaq-gui` | PyPI | `pkg:pypi/pymodaq-gui` | All versions | 5.1.15 |
| `pymodaq-gui` | PyPI | `pkg:pypi/pymodaq-gui` | From 5.2.0 | 5.2.14 |
| `pymodaq-gui` | PyPI | `pkg:pypi/pymodaq-gui` | From 5.3.0 | 5.3.10 |
| `pymodaq-utils` | PyPI | `pkg:pypi/pymodaq-utils` | All versions | 5.1.15 |
| `pymodaq-utils` | PyPI | `pkg:pypi/pymodaq-utils` | From 5.2.0 | 5.2.14 |
| `pymodaq-utils` | PyPI | `pkg:pypi/pymodaq-utils` | From 5.3.0 | 5.3.10 |

## How do I fix CVE-2026-120859?

Upgrade pymodaq-data to a fixed version for your release line: 5.1.15, 5.2.14 or 5.3.10.

## Is CVE-2026-120859 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120859 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-120859 and fix it if it is affected.

What it is: CVE-2026-120859 is a high-severity vulnerability in PyMoDAQ, published on 5 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-120859 exists.

Affected packages and fixed versions:
- pymodaq-data (PyPI): affected all versions; fixed in 5.1.15
- pymodaq-data (PyPI): affected from 5.2.0; fixed in 5.2.14
- pymodaq-data (PyPI): affected from 5.3.0; fixed in 5.3.10
- pymodaq (PyPI): affected all versions; fixed in 4.4.13
- pymodaq-gui (PyPI): affected all versions; fixed in 5.1.15
- pymodaq-gui (PyPI): affected from 5.2.0; fixed in 5.2.14
- pymodaq-gui (PyPI): affected from 5.3.0; fixed in 5.3.10
- pymodaq-utils (PyPI): affected all versions; fixed in 5.1.15
- pymodaq-utils (PyPI): affected from 5.2.0; fixed in 5.2.14
- pymodaq-utils (PyPI): affected from 5.3.0; fixed in 5.3.10

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-120859/ (Markdown: https://insights.sbomify.com/CVE-2026-120859/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-120859
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-120859
- OSV: https://osv.dev/vulnerability/CVE-2026-120859

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-120859/
Summaries are generated and may contain mistakes; the official description above is the record.
