critical CVSS 10

CVE-2026-33054·Python vulnerability

Mesop 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.

Severity: critical
Software: Python
Fixed in: 1.2.3
Published: 2026-03-20

Affected versions

Until: 1.2.3

Fixed in: 1.2.3

How to fix this CVE

Upgrade Mesop to version 1.2.3 or later to patch a critical path traversal vulnerability in the FileStateSessionBackend. This vulnerability allows attackers to manipulate state_token values to access arbitrary files on disk, potentially causing denial of service or data corruption. Immediately update your Mesop installation and restart all affected applications.

sudo dnf update python3-mesop

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

POST requests to Mesop UI endpoints containing state_token parameters with path traversal patterns such as: state_token=.*(\.\./|\.\.\\|%2e%2e%2f|%2e%2e%5c).*

WAF mitigation (if patching is not yet possible)

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

Block or sanitize any state_token parameter values containing path traversal sequences (../, .., encoded variants %2e%2e). Implement strict input validation to reject state_token values that don't match expected base64 or hash format patterns for your Mesop application.

How to check if you are affected

Step 1: Check installed Mesop version with: python3 -c "import mesop; print(mesop.__version__)"
Step 2: Verify if FileStateSessionBackend is configured by searching your application config files for 'FileStateSessionBackend' or checking environment variables with: env | grep -i mesop
Step 3: Review application logs for suspicious state_token patterns in UI stream payloads, looking for entries containing path traversal sequences (../, ..\, or encoded variants) in request parameters
Step 4: Confirm the patch was applied by re-running the version check command and verifying output is 1.2.3 or higher

FAQ

What is CVE-2026-33054?

CVE-2026-33054 is a critical path traversal vulnerability in Mesop (Python UI framework) versions 1.2.2 and below that allows attackers to manipulate the state_token parameter to read, write, or delete arbitrary files on the server when using FileStateSessionBackend.

Is CVE-2026-33054 being actively exploited?

No, CVE-2026-33054 is not listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available, though the vulnerability is easily exploitable and should be treated with urgency.

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

The vulnerability affects Mesop versions 1.2.2 and below. All versions of Python 3 running vulnerable Mesop versions are at risk, particularly those configured with FileStateSessionBackend for session state management.

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

Run: python3 -c "import mesop; print(mesop.__version__)" and confirm the version is 1.2.3 or higher. Also verify your application config uses FileStateSessionBackend by checking configuration files or running: grep -r "FileStateSessionBackend" /path/to/app/

Does Defensia detect CVE-2026-33054?

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

Related Python CVEs

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-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-2026-25632CVSS 10EPyT-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.

CVE-2026-9135CVSS 9.9IBM Langflow OSS 1.0.0 through 1.10.0 Langflow versions up to 1.9.2 (commit 94981c443d4918517b9e8163d70fc598dc33a32d) contain a code injection vulnerability in the Policies component's ToolGuard integration that bypasses the allow_custom_components=false security control. The vulnerability exists because the validation mechanism only checks the main component source code in node_template["code"]["value"] but fails to validate dynamic CodeInput fields that store generated ToolGuard Python files. Attackers can embed malicious Python code in these unvalidated dynamic fields, which are persisted in Flow.data and later executed server-side when a guarded tool is invoked through the ToolGuard runtime. This allows authenticated users with flow creation privileges to achieve arbitrary Python code execution on the backend despite custom component restrictions. The vulnerability can be escalated through cross-tenant flow manipulation via the agentic MCP update_flow_component_field tool, which accepts attacker-controlled user_id parameters, enabling attackers to inject malicious code into victim users' flows. When combined with publicly accessible flows and specific misconfigurations (AUTO_LOGIN=true, NEW_USER_IS_ACTIVE=true), the attack can be conducted with reduced authentication requirements.

CVE-2026-25115CVSS 9.9n8n is an open source workflow automation platform. Prior to version 2.4.8, a vulnerability in the Python Code node allows authenticated users to break out of the Python sandbox environment and execute code outside the intended security boundary. This issue has been patched in version 2.4.8.

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-33054. Free for 1 server.

Get started free