# CVE-2026-54695: Pipecat: Telephony WebSocket `/ws` Unauthenticated Call-Control Abuse via Attacker-Supplied Call SID

> Unauthenticated WebSocket endpoint allows attackers to trigger authenticated Twilio API calls using server credentials, enabling unauthorized call control.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-j8cv-x86q-rj85, PYSEC-2026-2878

## What is CVE-2026-54695?

CVE-2026-54695 is a high-severity missing authorization vulnerability in pipecat-ai pipecat, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-54695?

3 open source packages ship an affected version, including pipecat-ai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pipecat-ai` | PyPI | From 0.0.77 | 1.4.0 |
| `pipecat-ai` | PyPI | From 0.0.77 | 1.4.0 |
| `pipecat-ai` | PyPI | From 0.0.77 | 1.4.0 |

Products: Pipecat Pipecat.

## How do I fix CVE-2026-54695?

Upgrade pipecat-ai to 1.4.0 or later.

## Is CVE-2026-54695 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54695 exists.

## Other vulnerabilities in pipecat-ai pipecat

- [CVE-2025-62373](https://insights.sbomify.com/CVE-2025-62373/): Pipecat vulnerable to Remote Code Execution by Pickle Deserialization via LivekitFrameSerializer (critical 9.8)
- [CVE-2026-44716](https://insights.sbomify.com/CVE-2026-44716/): Pipecat: Path Traversal in Pipecat Runner `/files` Endpoint — Arbitrary File Read via `%2F`-Encoded Separator (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-54695 and fix it if it is affected.

What it is: CVE-2026-54695 is a high-severity missing authorization vulnerability in pipecat-ai pipecat, published on 9 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54695 exists.

Affected packages and fixed versions:
- pipecat-ai (PyPI): affected from 0.0.77; fixed in 1.4.0
- pipecat-ai (PyPI): affected from 0.0.77; fixed in 1.4.0
- pipecat-ai (PyPI): affected from 0.0.77; fixed in 1.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-54695/ (Markdown: https://insights.sbomify.com/CVE-2026-54695/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-54695
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-54695
- OSV: https://osv.dev/vulnerability/CVE-2026-54695

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-54695/
Summaries are generated and may contain mistakes; the official description above is the record.