Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
EPyT-Flow, a Python package, is vulnerable to unsafe JSON deserialization in versions before 0.16.1. Its REST API and JSON file loading use a custom deserializer that dynamically imports and instantiates attacker-specified classes when a __type__ field is present, which the source says can lead to OS command execution during parsing. The source does not state what access an attacker needs beyond supplying crafted JSON. Upgrade to epyt-flow 0.16.1, which contains the fix; until then, the source advises not loading JSON from untrusted sources and not exposing the REST API.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 10.0 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0080, the 56th percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-74vm-8frp-7w68
- OSV: GHSA-74vm-8frp-7w68
- github.com/WaterFutures/EPyT-Flow/security/advisories/GHSA-74vm-8frp-7w68
- nvd.nist.gov/vuln/detail/CVE-2026-25632
- github.com/WaterFutures/EPyT-Flow/commit/3fff9151494c7dbc72073830b734f0a7e550e385
- github.com/WaterFutures/EPyT-Flow
- github.com/WaterFutures/EPyT-Flow/releases/tag/v0.16.1
- github.com/pypa/advisory-database/tree/main/vulns/epyt-flow/PYSEC-2026-330.yaml
- pypi.org/project/epyt-flow