high CVSS 7.5

CVE-2026-44716·Python vulnerability

Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. From version 0.0.90 to before version 1.2.0, a path traversal vulnerability exists in Pipecat's development runner (src/pipecat/runner/run.py). When the runner is started with the --folder flag, it exposes a GET /files/{filename:path} download endpoint. The filename path parameter is concatenated directly onto args.folder with no containment check. Starlette normalises literal ../ sequences in URLs, but %2F-encoded slashes bypass this normalisation: the path parameter is URL-decoded after routing, so ..%2F..%2Fetc%2Fpasswd resolves to a path two levels above args.folder. An attacker with network access to the runner can read any file the pipecat process has permission to access — including SSH private keys, credentials, and system files — with a single unauthenticated HTTP request. This issue has been patched in version 1.2.0.

Severity: high
Software: Python
Fixed in: 1.2.0
Published: 2026-06-10

Affected versions

From: 0.0.90

Until: 1.2.0

Fixed in: 1.2.0

How to fix this CVE

Upgrade Pipecat to version 1.2.0 or later to patch the path traversal vulnerability in the development runner's file download endpoint. If you are running Pipecat with the --folder flag exposed to untrusted networks, immediately restrict network access to the runner until the upgrade is completed. Review your logs for any suspicious file access attempts targeting paths outside your intended folder.

sudo dnf upgrade python3-pipecat

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

GET /files/.*\.\.%2F|GET /files/.*\.\.%2F.*\.\.(passwd|ssh|key|credentials)

WAF mitigation (if patching is not yet possible)

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

Block requests to GET /files/ endpoint containing URL-encoded path traversal sequences (%2F, %2e%2e). Implement a whitelist of allowed filenames and reject any requests containing path separators or parent directory references. Consider requiring authentication for the /files/ endpoint.

How to check if you are affected

Check Pipecat version: pip show pipecat | grep Version
Verify if the runner is active: ps aux | grep 'pipecat.*--folder' to see if the vulnerable --folder flag is in use
Search logs for GET /files/ requests: grep -r 'GET /files/' /var/log/ to identify any file download attempts
Confirm the fix: pip show pipecat should report version 1.2.0 or higher after upgrade

Indicators of compromise

GET /files/ endpoint requests with %2F or %2e%2e sequences
Access attempts to /files/ endpoints targeting /etc/passwd, ~/.ssh/, or credential paths

FAQ

What is CVE-2026-44716?

CVE-2026-44716 is a path traversal vulnerability in Pipecat's development runner that allows unauthenticated attackers to download arbitrary files from the server by encoding path traversal sequences in HTTP requests to the /files/ endpoint.

Is CVE-2026-44716 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploit code is available.

What versions of Pipecat are affected by CVE-2026-44716?

Pipecat versions 0.0.90 through 1.1.x are vulnerable; version 1.2.0 and later contain the fix.

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

Run: pip show pipecat | grep Version. If the version is below 1.2.0 and you use the --folder flag, your installation is vulnerable.

Does Defensia detect CVE-2026-44716?

Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If Pipecat is installed on a monitored server, CVE-2026-44716 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-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-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.

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

Get started free