{"answers":{"affected":"3 open source packages ship an affected version, including epyt-flow. It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-25632 in the wild and no public exploit code.","fix":"Upgrade epyt-flow to 0.16.1 or later.","what":"CVE-2026-25632 is a critical unsafe deserialization vulnerability in WaterFutures EPyT-Flow, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-25632 and fix it if it is affected.\n\nWhat it is: CVE-2026-25632 is a critical unsafe deserialization vulnerability in WaterFutures EPyT-Flow, published on 6 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-25632 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- epyt-flow (PyPI): affected all versions; fixed in 0.16.1\n- epyt-flow (PyPI): affected all versions; fixed in 0.16.1\n- epyt-flow (PyPI): affected all versions; fixed in 0.16.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-25632/ (Markdown: https://insights.sbomify.com/CVE-2026-25632/index.md)","id":"CVE-2026-25632","markdown":"https://insights.sbomify.com/CVE-2026-25632/index.md","name":"CVE-2026-25632","record":{"aliases":["GHSA-74vm-8frp-7w68","PYSEC-2026-330"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python water network library","requires_auth":"none","summary":"Attackers can execute arbitrary OS commands by sending malicious JSON payloads to the EPyT-Flow REST API or loading crafted files.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"epyt-flow","vendor":"waterfutures"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":"2026-07-21","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-07-21T23:00:44Z","kind":"github_poc","ref":"https://github.com/lazarus0x1337/CVE-2026-25632","stars":1,"title":"CVE-2026-25632 — Fix Unsafe JSON Deserialization Leading to Remote Code Execution"}],"tier":"poc_unverified"},"has_fix":true,"headline":"EPyT-Flow has unsafe JSON deserialization (__type__)","id":"CVE-2026-25632","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"Statamic's missing authorization allows access to assets","id":"CVE-2026-25633"},"packages":[{"ecosystem":"PyPI","fixed":["0.16.1"],"introduced":["0"],"last_affected":[],"package":"epyt-flow","purl":null,"source":"GHSA-74vm-8frp-7w68"},{"ecosystem":"PyPI","fixed":["0.16.1"],"introduced":["0"],"last_affected":[],"package":"epyt-flow","purl":"pkg:pypi/epyt-flow","source":"GHSA-74vm-8frp-7w68"},{"ecosystem":"PyPI","fixed":["0.16.1"],"introduced":["0"],"last_affected":[],"package":"epyt-flow","purl":"pkg:pypi/epyt-flow","source":"PYSEC-2026-330"}],"prev":{"headline":"Domain allowlist bypass enables credential exfiltration","id":"CVE-2026-25631"},"products":["EPyT-Flow"],"published":"2026-02-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-02-06","vendors":["WaterFutures"]},"summary":"Attackers can execute arbitrary OS commands by sending malicious JSON payloads to the EPyT-Flow REST API or loading crafted files.","url":"https://insights.sbomify.com/CVE-2026-25632/"}