CVE-2026-25632 | EPyT-Flow has unsafe JSON deserialization (__type__)

EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water distribution networks. Prior to 0.16.1, EPyT-Flow’s REST API parses attacker-controlled JSON request bodies using a custom deserializer (my_load_from_json) that supports a type field. When type is present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-supplied arguments. This allows invoking dangerous classes such as subprocess.Popen, which can lead to OS command execution during JSON parsing. This also affects the loading of JSON files. This vulnerability is fixed in 0.16.1.

Published: 2026-02-06 Last update: 2026-03-18 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-25632 is rated Moderate Risk (48.1/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.08%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-25632

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-19 0.04% 0.08% +0.04%
2 2026-02-18 0.11% 0.04% -0.06%
3 2026-02-07 0.11%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-25632

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
10.0 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C)
Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9 6.0 [email protected]

Weakness enumeration for CVE-2026-25632

GitHub Security Advisory for CVE-2026-25632

GHSA-74vm-8frp-7w68 · Severity: critical · Ecosystem: pip — EPyT-Flow vulnerable to unsafe JSON deserialization (__type__)

Affected software / configurations for CVE-2026-25632

Vendor Product Version Raw CPE
waterfutures epyt-flow < 0.16.1 cpe:2.3:a:waterfutures:epyt-flow:*:*:*:*:*:python:*:*

References for CVE-2026-25632

cvelogic Threat Intelligence