CVE-2026-54695 pipecat 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.
Quick answer
pipecat should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Review vendor advisory for affected versions.
Fixed versions
- Apply the latest vendor-supported patched version.
How to fix it
Pipecat is affected by CVE-2026-54695, a security exposure. Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. The recommended remediation is to update to Pipecat 1.4.0 or later. Until the update is complete, disable or bind the development /ws telephony testing endpoint to trusted localhost-only access, review logs, and reduce exposure of the affected service or workflow.
- Inventory every deployment, package, appliance, container, service, and managed environment that uses Pipecat.
- Confirm the installed version and compare it with the affected versions listed in the source advisory and the source advisory for CVE-2026-54695.
- Apply the vendor-supported fix: update to Pipecat 1.4.0 or later.
- If the update cannot be applied immediately, disable or bind the development /ws telephony testing endpoint to trusted localhost-only access; disable unnecessary public access, endpoints, plugins, integrations, or management interfaces until patched.
- Review application, device, reverse-proxy, WAF, package manager, container, authentication, and audit logs for activity related to CVE-2026-54695.
- Rotate sessions, API tokens, service credentials, integration keys, and administrator passwords if logs or affected data indicate compromise or unauthorized access.
- Clear caches, restart affected services, rebuild affected containers or appliances when appropriate, and remove temporary files or stored payloads created during exploitation attempts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm Pipecat now reports Pipecat 1.4.0 or later or a later vendor-supported fixed release for the deployed branch.
- Verify the affected workflow no longer allows the behavior described in CVE-2026-54695, using a safe regression test or vendor-provided validation method.
- Review logs after remediation for continued exploit attempts, denial-of-service symptoms, suspicious redirects, unauthorized requests, file access, or configuration changes.
- Rerun a Fixnx scan and any product-specific scanner, package audit, device health check, or manual regression test relevant to the affected service.
- Document affected assets, fixed versions, mitigation decisions, validation evidence, and any cleanup or credential rotation performed.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-54695?
pipecat should be checked against the vendor advisory and trusted references linked on this page.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.