CVE-2026-25632 EPyT-Flow has unsafe JSON deserialization (__type__)
- Published
- Updated
- Exploit status
- No public exploit known
- CISA SSVC
- No known exploitation · automatable: yes · technical impact: total
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.
Upgrade path
2 packages: 2 fixed.
| Package | Affected | Fixed in | Status |
|---|---|---|---|
| pypi epyt-flow(PyPI) | < 0.16.1; = 0.1.0; = 0.1.1; = 0.2.0 +22 more | 0.16.1 | Fixed |
| WaterFutures EPyT-Flow | < 0.16.1; = < 0.16.1 | 0.16.1 | Fixed |
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| pypi epyt-flow(PyPI) | < 0.16.1 | 0.16.1 |
| pypi epyt-flow(PyPI) | = 0.1.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.1.1 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.10.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.11.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.12.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.13.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.13.1 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.14.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.14.1 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.14.2 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.15.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.15.0b1 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.16.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.2.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.3.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.4.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.5.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.6.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.7.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.7.1 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.7.2 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.7.3 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.8.0 | No fix listed |
| pypi epyt-flow(PyPI) | = 0.8.1 | No fix listed |
Show 3 more
| Product | Affected versions | Fixed in |
|---|---|---|
| pypi epyt-flow(PyPI) | = 0.9.0 | No fix listed |
| WaterFutures EPyT-Flow | = < 0.16.1 | No fix listed |
| WaterFutures EPyT-Flow | < 0.16.1 | 0.16.1 |
References
- https://github.com/WaterFutures/EPyT-Flow/security/advisories/GHSA-74vm-8frp-7w68 vendor-advisory
- nvd.nist.gov third-party-advisory vendor-advisory
- https://github.com/WaterFutures/EPyT-Flow/commit/3fff9151494c7dbc72073830b734f0a7e550e385 patch
- github.com product
- https://github.com/WaterFutures/EPyT-Flow/releases/tag/v0.16.1 product release-notes
- github.com
- pypi.org product
- github.com vendor-advisory