CVE-2026-54695: Pipecat missing authorization in development runner WebSocket endpoints

CVE-2026-54695 · Severity: high · CVSS 7.5 · Published 2026-07-09

Pipecat is an open-source framework used to build voice-based AI agents that interact with telephony services like Twilio. In versions prior to 1.4.0, a development component fails to properly verify the identity of incoming connections. This allows an unauthorized person to remotely terminate active phone calls or disrupt services by sending specially crafted messages to the server.

Technologies: pipecat-ai (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-54695 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-54695 being exploited in the wild.
How severe is CVE-2026-54695?
High severity, with a CVSS score of 7.5, published 9 July 2026.
Which products and versions are affected?
Pipecat AI Pipecat < 1.4.0, >= 0.0.77, < 1.4.0; pipecat-ai (PyPI) >= 0.0.77, < 1.4.0, ECOSYSTEM:introduced=0.0.77,fixed=1.4.0.
Is there a fix for CVE-2026-54695?
Yes. pipecat-ai (PyPI): upgrade to 1.4.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-54695 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-54695?
Check whether you run Pipecat AI Pipecat or pipecat-ai (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • pipecat-ai (PyPI): upgrade to 1.4.0 or later
    pip install "pipecat-ai>=1.4.0"

Technical details

A missing authorization vulnerability (CWE-862) exists in the Pipecat development runner's /ws and /ws-client WebSocket endpoints. Prior to version 1.4.0, the runner accepted unauthenticated connections and processed attacker-supplied identifiers (such as Twilio's callSid) from stream-start handshakes. These identifiers were then passed to internal serializers, causing the server to issue authenticated REST API 'hang-up' requests using the server operator's stored credentials. This allows a remote, unauthenticated attacker to perform unauthorized call control actions. The fix introduces optional HMAC-SHA256 token authentication for WebSocket connections, requiring a signed session token obtained via a POST /start request.

Affected products

  • pipecat-ai Pipecat < 1.4.0

Identifiers

  • CVE-2026-54695
  • GHSA-j8cv-x86q-rj85
  • PYSEC-2026-2878

Timeline

  • 2026-06-08: patched: HMAC token authentication merged into main branch
  • 2026-07-09: advisory: NVD and GitHub Security Advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.