Epyt FlowApplication · Waterfutures
CVE-2026-25632
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEPyT-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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEPyT-Flow's REST API uses a custom JSON deserializer (my_load_from_json) that supports a 'type' field. When present, the deserializer dynamically imports an attacker-specified module/class and instantiates it with attacker-controlled arguments, enabling execution of dangerous classes like subprocess.Popen for OS command execution. This also affects JSON file loading.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Epyt FlowApplication
< 0.16.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if Epyt Flow is installedLocate the Epyt Flow installation by searching for its package directory, configuration files, or running processes named 'epytflow' or similarAffected if Epyt Flow is found installed on the system
-
Determine installed versionCheck the version of Epyt Flow using package management tools, pip list, or examining version files within the installation directoryAffected if The installed version is lower than 0.16.1 (e.g., 0.16.0, 0.15.x, etc.)
-
Verify REST API is enabledInspect configuration files or running services to confirm the REST API component is active. Look for API-related settings, listening ports, or service definitionsAffected if The REST API is enabled and running
-
Confirm JSON file loading is availableExamine whether the JSON file loading functionality is accessible through the API endpoints or if the my_load_from_json function can be invokedAffected if JSON file loading or the custom deserializer is accessible via API or file processing
-
Check network exposure of REST APIReview network bindings, firewall rules, or service configuration to determine if the REST API is exposed to untrusted networksAffected if The REST API is accessible from network locations beyond localhost
The environment is affected if Epyt Flow version is below 0.16.1 AND the REST API with JSON deserialization functionality is enabled and accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.16.1
Upgrade to version 0.16.1 or later to patch the insecure deserialization vulnerability. If immediate patching is not feasible, restrict network access to the REST API and disable JSON file loading functionality as a temporary measure.
0.16.1
- Upgrade EPyT-Flow to version 0.16.1 or later using pip: pip install epytflow>=0.16.1
- Verify the upgrade was successful by running: pip show epytflow and checking the version number
- Restart any running EPyT-Flow services to ensure the new version is loaded
- If in production, deploy the upgrade to a staging environment first and test that EPyT-Flow functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Epyt Flow
Scoped from the published advisory
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-25632 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-25632 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data