Vulnerability · Published Feb 6, 2026 · Assigned by GitHub_M
CVE-2026-25632EPyT-Flow has unsafe JSON deserialization (__type__)
Critical 10.0
In plain English
A critical-severity unsafe deserialization in EPyT-Flow from WaterFutures. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.8% (higher than 57% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.
Official description
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.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| PyPI | epyt-flow | 0.16.1 | GHSA-74vm-8frp-7w68 |
| PyPI | epyt-flow | 0.16.1 | PYSEC-2026-330 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| WaterFutures | EPyT-Flow | < 0.16.1 |
Weakness: CWE-502 · Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H