WaterFutures EPyT-Flow
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 0.16.1
Fixed in 0.16.1
Mitigation
Upgrade EPyT-Flow to 0.16.1 or later.
References
- Vendor advisory github.com/WaterFutures/EPyT-Flow/security/adv…
- Patch github.com/WaterFutures/EPyT-Flow/commit/3fff9…
- Release notes github.com/WaterFutures/EPyT-Flow/releases/tag…
Timeline
Days relative to CVE publicationFirst public PoC 165 days after publication; not in CISA KEV. First PoC: lazarus0x1337/CVE-2026-25632 (created 21 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| lazarus0x1337/CVE-2026-25632 | 21 Jul 2026 +165 d | 1 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.