CVE-2026-25632: EPyT-Flow vulnerable to unsafe JSON deserialization (__type__)
Affects epyt-flowSource GCVE Database
Not known to be exploited · CVSS 10.0 Critical : upgrade to 0.16.1 as a priority.
Data as of 27 Oct 2026, 17:31 UTC
- Patch
- Available – fixed in 0.16.1
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade epyt-flow to 0.16.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIepyt-flow | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in EPyT-Flow version 0.16.1; users should upgrade to this version or later. Until patched, avoid loading JSON data from untrusted sources and do not expose the REST API to untrusted networks.
Description
EPyT-Flow versions up to 0.16.0 contain a critical vulnerability in their REST API where unsafe JSON deserialization allows attackers to specify a __type__ field. This enables dynamic import and instantiation of arbitrary classes, including dangerous ones like subprocess.Popen, leading to remote OS command execution. The vulnerability is fixed in version 0.16.1. Users should avoid loading JSON from untrusted sources and not expose the REST API until patched.
References
- github.com/WaterFutures/EPyT-Flow/security/advisories/GHSA-74vm-8frp-7w68 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-25632 (opens in a new tab)
- github.com/WaterFutures/EPyT-Flow/commit/3fff9151494c7dbc72073830b734f0a7e550e385 (opens in a new tab)
- github.com/WaterFutures/EPyT-Flow (opens in a new tab)
- github.com/WaterFutures/EPyT-Flow/releases/tag/v0.16.1 (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/epyt-flow/PYSEC-2026-330.yaml (opens in a new tab)
- pypi.org/project/epyt-flow (opens in a new tab)