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.
CVE-2026-120859
HIGHPre-NVD 7.87.8ElevatedEG-KEV Tier 3: ElevatedEG-KEV is EchelonGraph's own tiering of exploitation signals from CISA KEV, CISA's SSVC data (Vulnrichment), ransomware data, public exploit-code references and EPSS.Tier 3 is not evidence of exploitation. It means public exploit code is referenced, or CISA's SSVC data says "public PoC", or EPSS ranks the CVE in the top 5%.Signals for this CVE: CISA's SSVC exploitation value: public PoC.EchelonGraph confidence 38%: a heuristic from the tier and the number of signals, not a measured probability.
EchelonGraph scoreMEDIUM confidence
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Also known asEUVD-2026-117605 (ENISA EUVD)Source: ENISA EUVD
7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 7.8HIGHmedium confidence
- EG Risk
- 51EG Risk 51/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity78% × 45%Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.2%
- EPSS %ILE
- 8th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 5, 2026
Last Modified
November 12, 2026
Advisory Details (10)
Auto-updated Nov 5, 2026Patch available. Sources: github, github_commit, github_release.
Web page
PyMoDAQ/packages/pymodaq_data/src/pymodaq_data/h5modules/backends.py at 5.3.9 · PyMoDAQ/PyMoDAQ · GitHub
https://github.com/PyMoDAQ/PyMoDAQ/blob/5.3.9/packages/pymodaq_data/src/pymodaq_data/h5modules/backends.py#L477-L478GitHub release Patch Available
4.4.13
Patch available: PyMoDAQ/PyMoDAQ 4.4.13
https://github.com/PyMoDAQ/PyMoDAQ/releases/tag/4.4.13GitHub release Patch Available
5.1.15
Patch available: PyMoDAQ/PyMoDAQ 5.1.15
https://github.com/PyMoDAQ/PyMoDAQ/releases/tag/5.1.15GitHub release Patch Available
5.2.14
Patch available: PyMoDAQ/PyMoDAQ 5.2.14
https://github.com/PyMoDAQ/PyMoDAQ/releases/tag/5.2.14GitHub release Patch Available
5.3.10
Patch available: PyMoDAQ/PyMoDAQ 5.3.10
https://github.com/PyMoDAQ/PyMoDAQ/releases/tag/5.3.10GitHub commit Patch Available
commit 041e8a22b3db (PyMoDAQ/PyMoDAQ)
Patch available: PyMoDAQ/PyMoDAQ 5.3.10 (contains commit 041e8a22b3db)
https://github.com/PyMoDAQ/PyMoDAQ/commit/041e8a22b3dbe3c986ec0ea3c6b46a22f5efe374GitHub commit Patch Available
commit ae0042513eb9 (PyMoDAQ/PyMoDAQ)
Patch available: PyMoDAQ/PyMoDAQ 5.3.10 (contains commit ae0042513eb9)
https://github.com/PyMoDAQ/PyMoDAQ/commit/ae0042513eb979c84da690825902658c625718d1GitHub commit Patch Available
commit 3bf9042a58f5 (PyMoDAQ/PyMoDAQ)
Patch available: PyMoDAQ/PyMoDAQ 5.3.10 (contains commit 3bf9042a58f5)
https://github.com/PyMoDAQ/PyMoDAQ/commit/3bf9042a58f5d4870a2b45fe2c9423aafe6b9203GitHub commit Patch Available
commit 6c7fff74d826 (PyMoDAQ/PyMoDAQ)
Patch available: PyMoDAQ/PyMoDAQ 5.3.10 (contains commit 6c7fff74d826)
https://github.com/PyMoDAQ/PyMoDAQ/commit/6c7fff74d82624c640bd79513f5b4675ea6d88daGitHub advisoryMentions a patch (unverified)
String evaluation · Advisory · PyMoDAQ/PyMoDAQ · GitHub
https://github.com/PyMoDAQ/PyMoDAQ/security/advisories/GHSA-jw9g-5c9x-cf84Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 10× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-12 21:28 UTCEchelonGraph re-scored
- 2026-11-12 16:33 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-11 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-11 03:47 UTCEchelonGraph re-scored
- 2026-11-10 16:42 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-09 23:47 UTCEchelonGraph re-scored
- 2026-11-09 22:41 UTCEchelonGraph re-scored
- 2026-11-09 22:30 UTCEchelonGraph re-scored
- 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-06 16:36 UTCEPSS rescoreEPSS 0.2% · 8th percentile
- 2026-11-05 18:27 UTCEchelonGraph re-scored
- 2026-11-05 18:04 UTCENISA EUVD ID recordedEUVD-2026-117605 · Source: ENISA EUVD
- 2026-11-05 17:24 UTCEchelonGraph re-scoredFirst assessed: 7.8 HIGH
- 2026-11-05 17:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-120859?
CVE-2026-120859 is a high-severity vulnerability; its CVE record was published on November 5, 2026. 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…
When was CVE-2026-120859 made public?
CVE-2026-120859 was made public on November 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on November 5, 2026. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-120859 actively exploited?
CVE-2026-120859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-120859?
CVE-2026-120859 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-120859?
A fix for CVE-2026-120859 is available: update to the fixed version the vendor names in its advisory.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-120859
Is Your Infrastructure Affected by CVE-2026-120859?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.