critical CVSS 10

CVE-2026-25632·Python vulnerability

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.

Severity
critical
Software
Python
Fixed in
0.16.1
Published
2026-02-06

Affected versions

Until: 0.16.1

Fixed in: 0.16.1

How to fix this CVE

Update EPyT-Flow to version 0.16.1 or later to patch the insecure JSON deserialization vulnerability. This vulnerability allows arbitrary code execution through malicious JSON payloads with crafted type fields. If you use EPyT-Flow in production, prioritize this update immediately given the critical CVSS 10.0 rating.

sudo dnf update python3-epyt-flow || pip3 install --upgrade epyt-flow>=0.16.1

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST|GET request containing JSON with '"type":"subprocess.Popen"' or similar dangerous class instantiation patterns in request body; HTTP requests to EPyT-Flow REST API endpoints with 'args' or 'kwargs' fields paired with OS-level class references

WAF mitigation (if patching is not yet possible)

Add this rule to your WAF to block exploitation attempts while you schedule the patch. 

Block HTTP requests to EPyT-Flow REST API endpoints containing JSON bodies with 'type' field set to known dangerous classes (subprocess, os, sys, eval, exec, __import__); implement strict Content-Type validation and JSON schema validation requiring absence of 'type' fields in untrusted inputs

How to check if you are affected

  1. Check installed EPyT-Flow version: pip3 show epyt-flow | grep Version
  2. Verify if EPyT-Flow REST API is exposed: netstat -tlnp | grep -E ':(5000|8000|8080)' and check application logs for REST endpoint listeners
  3. Search application logs for suspicious JSON payloads with 'type' field and class instantiation attempts: grep -r '"type".*subprocess\|"type".*Popen\|"type".*os\.' /var/log/
  4. Confirm patched version is running: pip3 show epyt-flow | grep Version && python3 -c 'import epyt_flow; print(epyt_flow.__version__)' to verify version >= 0.16.1

FAQ

What is CVE-2026-25632?

CVE-2026-25632 is a critical remote code execution vulnerability in EPyT-Flow's JSON deserialization logic that allows attackers to instantiate arbitrary Python classes and execute system commands by including a malicious 'type' field in JSON requests or files sent to the REST API.

Is CVE-2026-25632 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog, and no public exploits have been disclosed, though the critical nature of the flaw makes it a high-priority target for attackers.

What versions of Python are affected by CVE-2026-25632?

All versions of EPyT-Flow prior to 0.16.1 are affected. The vulnerability exists in the custom JSON deserializer (my_load_from_json) used by the REST API and JSON file loading functions.

How do I check if my server is vulnerable to CVE-2026-25632?

Run 'pip3 show epyt-flow | grep Version' and verify the version is 0.16.1 or higher. If the version is below 0.16.1, your system is vulnerable.

Does Defensia detect CVE-2026-25632?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If EPyT-Flow is installed on a monitored server, CVE-2026-25632 will appear in your dashboard with remediation steps.

Related Python CVEs

CVE-2026-33054CVSS 10Mesop is a Python-based UI framework that allows users to build web applications. Versions 1.2.2 and below contain a Path Traversal vulnerability that allows any user supplying an untrusted state_token through the UI stream payload to arbitrarily target files on the disk under the standard file-based runtime backend. This can result in application denial of service (via crash loops when reading non-msgpack target files as configurations), or arbitrary file manipulation. This vulnerability heavily exposes systems hosted utilizing FileStateSessionBackend. Unauthorized malicious actors could interact with arbitrary payloads overwriting or explicitly removing underlying service resources natively outside the application bounds. This issue has been fixed in version 1.2.3.
CVE-2026-28505CVSS 10Tautulli is a Python based monitoring and tracking tool for Plex Media Server. Prior to version 2.17.0, the str_eval() function in notification_handler.py implements a sandboxed eval() for notification text templates. The sandbox attempts to restrict callable names by inspecting code.co_names of the compiled code object. However, co_names only contains names from the outer code object. When a lambda expression is used, it creates a nested code object whose attribute accesses are stored in code.co_consts, NOT in code.co_names. The sandbox never inspects nested code objects. This issue has been patched in version 2.17.0.
CVE-2026-32871CVSS 10FastMCP is a Pythonic way to build MCP servers and clients. Prior to version 3.2.0, the OpenAPIProvider in FastMCP exposes internal APIs to MCP clients by parsing OpenAPI specifications. The RequestDirector class is responsible for constructing HTTP requests to the backend service. A vulnerability exists in the _build_url() method. When an OpenAPI operation defines path parameters (e.g., /api/v1/users/{user_id}), the system directly substitutes parameter values into the URL template string without URL-encoding. Subsequently, urllib.parse.urljoin() resolves the final URL. Since urljoin() interprets ../ sequences as directory traversal, an attacker controlling a path parameter can perform path traversal attacks to escape the intended API prefix and access arbitrary backend endpoints. This results in authenticated SSRF, as requests are sent with the authorization headers configured in the MCP provider. This issue has been patched in version 3.2.0.
CVE-2026-34938CVSS 10PraisonAI is a multi-agent teams system. Prior to version 1.5.90, execute_code() in praisonai-agents runs attacker-controlled Python inside a three-layer sandbox that can be fully bypassed by passing a str subclass with an overridden startswith() method to the _safe_getattr wrapper, achieving arbitrary OS command execution on the host. This issue has been patched in version 1.5.90.
CVE-2025-54381CVSS 9.9BentoML is a Python library for building online serving systems optimized for AI apps and model inference. In versions 1.4.0 until 1.4.19, the file upload processing system contains an SSRF vulnerability that allows unauthenticated remote attackers to force the server to make arbitrary HTTP requests. The vulnerability stems from the multipart form data and JSON request handlers, which automatically download files from user-provided URLs without validating whether those URLs point to internal network addresses, cloud metadata endpoints, or other restricted resources. The documentation explicitly promotes this URL-based file upload feature, making it an intended design that exposes all deployed services to SSRF attacks by default. Version 1.4.19 contains a patch for the issue.

References

Track CVEs across your fleet automatically

Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-25632. Free for 1 server.

Get started free