CVE-2025-62373
published 2026-04-23CVE-2025-62373: Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. Versions 0.0.41 through 0.0.93 have a…
PriorityP267critical9.8CVSS 3.1
AVNACLPRNUINSUCHIHAH
EPSS
0.70%
48.5th percentile
Pipecat is an open-source Python framework for building real-time voice and multimodal conversational agents. Versions 0.0.41 through 0.0.93 have a vulnerability in `LivekitFrameSerializer` – an optional, non-default, undocumented frame serializer class (now deprecated) intended for LiveKit integration. The class's `deserialize()` method uses Python's `pickle.loads()` on data received from WebSocket clients without any validation or sanitization. This means that a malicious WebSocket client can send a crafted pickle payload to execute arbitrary code on the Pipecat server. The vulnerable code resides in `src/pipecat/serializers/livekit.py` (around line 73), where untrusted WebSocket message data is passed directly into `pickle.loads()` for deserialization. If a Pipecat server is configured to use LivekitFrameSerializer and is listening on an external interface (e.g. 0.0.0.0), an attacker on the network (or the internet, if the service is exposed) could achieve remote code execution (RCE) on the server by sending a malicious pickle payload. Version 0.0.94 contains a fix. Users of Pipecat should avoid or replace unsafe deserialization and improve network security configuration. The best mitigation is to stop using the vulnerable LivekitFrameSerializer altogether. Those who require LiveKit functionality should upgrade to the latest Pipecat version and switch to the recommended `LiveKitTransport` or another secure method provided by the framework. Additionally, always follow secure coding practices: never trust client-supplied data, and avoid Python pickle (or similar unsafe deserialization) in network-facing components.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| pipecat-ai | pipecat | — | — |
| pipecat | pipecat | >= 0.0.41 < 0.0.94 | 0.0.94 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
VulDB
pipecat-ai pipecat up to 0.0.93 Pickle livekit.py deserialize deserialization (EUVD-2025-209570)
vuldb·2026-04-23·CVSS 9.8
CVE-2025-62373 [CRITICAL] pipecat-ai pipecat up to 0.0.93 Pickle livekit.py deserialize deserialization (EUVD-2025-209570)
A vulnerability was found in pipecat-ai pipecat up to 0.0.93 and classified as critical. The impacted element is the function deserialize of the file src/pipecat/serializers/livekit.py of the component Pickle Handler. Executing a manipulation can lead to deserialization.
This vulnerability is handled as CVE-2025-62373. The attack can be executed remotely. There is not any exploit available.
It is suggested to upgrade the affected component.
GHSA
Pipecat: Remote Code Execution by Pickle Deserialization Through LivekitFrameSerializer
ghsa·2026-04-23
CVE-2025-62373 [CRITICAL] CWE-502 Pipecat: Remote Code Execution by Pickle Deserialization Through LivekitFrameSerializer
Pipecat: Remote Code Execution by Pickle Deserialization Through LivekitFrameSerializer
Remote Code Execution via Unsafe Deserialization in Pipecat's LivekitFrameSerializer
### Summary
A critical vulnerability exists in Pipecat's `LivekitFrameSerializer` – an **optional, non-default, undocumented** frame serializer class (now deprecated) intended for LiveKit integration. The class's `deserialize()` method uses Python's `pickle.loads()` on data received from WebSocket clients without any validation or sanitization. This means that a malicious WebSocket client can send a crafted pickle payload to execute arbitrary code on the Pipecat server. The vulnerable code resides in `src/pipecat/serializers/livekit.py` (around line 73), where untrusted WebSocket message data is passed directly into
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2026-04-23
Published