CVE Catalog

CVE-2025-62373

CriticalCVSS 9.8
Published: Updated: Translated: NVD NIST

Exploitation Probability (EPSS)

Elevated risk
0.70%

52th percentile - higher than 52% of all known CVEs

Summary

Pipecat versions 0.0.41 through 0.0.93 contain a vulnerability in the optional LivekitFrameSerializer class, whose deserialize() method uses pickle.loads() on data received from WebSocket clients without validation. A malicious WebSocket client can send a crafted pickle payload to execute arbitrary code on the Pipecat server (RCE). Version 0.0.94 contains a fix.

Risk Assessment

If a Pipecat server is configured to use LivekitFrameSerializer and listens on an external interface (e.g. 0.0.0.0), an attacker on the network or the internet can achieve remote code execution on the server. This can lead to full compromise of the service and potential data breach.

Recommendation

Stop using LivekitFrameSerializer and switch to the recommended LiveKitTransport or another secure method; upgrade Pipecat to version 0.0.94 or later. Restrict network exposure of the service and never use pickle for deserializing client-supplied data.

Other vulnerabilities in Pipecat

Original NVD description (English source)

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.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS