high CVSS 7.5 EPSS 0.37%

CVE-2026-54695·Python vulnerability

Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. Prior to 1.4.0, the pipecat development runner registers a /ws WebSocket endpoint for telephony testing that accepts connections without authentication, reads an attacker-supplied callSid from a Twilio stream-start handshake in src/pipecat/runner/utils.py, and passes it to TwilioFrameSerializer so the server can issue an authenticated Twilio REST API hang-up request with the server operator's credentials; equivalent unauthenticated call-control sinks exist for Telnyx and Plivo. This issue is fixed in version 1.4.0.

Severity
high
Software
Python
Fixed in
1.4.0
Published

How likely is exploitation

FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.37% — higher than 30% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.

Read the two together. CVE-2026-54695 scores 7.5 on CVSS, so a successful attack would be serious — but at 0.37%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.

Affected versions

Until: 1.4.0

Fixed in: 1.4.0

How to fix this CVE

Update Pipecat to version 1.4.0 or later to remove the unauthenticated WebSocket endpoint that exposes call-control functionality. Organizations running Pipecat development runners should immediately patch to prevent unauthorized call termination and credential misuse through the /ws telephony testing endpoint. Verify that authentication mechanisms are enforced on all WebSocket endpoints after upgrading.

sudo dnf update python3-pipecat || sudo pip3 install --upgrade pipecat>=1.4.0

Defensia detects this vulnerability

What an exploitation attempt looks like

Sample log line indicative of exploitation attempts:

WebSocket upgrade request to /ws endpoint with Twilio stream-start handshake containing callSid parameter followed by REST API hang-up request: POST /2010-04-01/Accounts/.*/Calls/[A-Za-z0-9]+ with no Bearer token in Authorization header

WAF mitigation (if patching is not yet possible)

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

Block all unauthenticated WebSocket connections to /ws endpoint. Implement strict authentication checks on WebSocket upgrade requests and reject any stream-start handshakes lacking valid OAuth/API credentials. Rate-limit WebSocket connection attempts to /ws from untrusted sources.

How to check if you are affected

  1. Run `pip3 show pipecat | grep Version` to identify the installed Pipecat version and compare it against 1.4.0.
  2. Check your application startup logs for WebSocket server initialization and confirm the /ws endpoint is bound to a restricted interface (not 0.0.0.0 or public IPs).
  3. Search application logs for WebSocket connection attempts with callSid parameters: `grep -i 'callsid\|stream-start' /var/log/pipecat.log` to identify suspicious handshake attempts.
  4. Verify the vulnerability is patched by checking the Pipecat source in `src/pipecat/runner/utils.py` contains authentication validation before processing TwilioFrameSerializer requests.

FAQ

What is CVE-2026-54695?

CVE-2026-54695 is an authentication bypass vulnerability in Pipecat's development runner that exposes an unauthenticated WebSocket endpoint allowing attackers to inject arbitrary Twilio call IDs and terminate calls using the server operator's credentials.

Is CVE-2026-54695 being actively exploited?

No, this vulnerability is not currently listed on the CISA Known Exploited Vulnerabilities (KEV) catalog and no public exploits are available at this time.

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

All Pipecat versions prior to 1.4.0 are vulnerable. The vulnerability affects the development runner's WebSocket implementation and also impacts equivalent endpoints in Telnyx and Plivo integrations.

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

Run `pip3 show pipecat` and verify the version is 1.4.0 or higher. Additionally, check if the development runner's WebSocket endpoint is exposed on a network interface: `netstat -tlnp | grep :8000` (if running on default port) and verify authentication is enforced.

Does Defensia detect CVE-2026-54695?

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

Get started free