Advisory record · GHSA-c2jg-5cp7-6wc7

Pipecat: Remote Code Execution by Pickle Deserialization Through LivekitFrameSerializer

CVSS 9.8 CriticalCriticalEPSS 0.0070 · 53rd percentile

Critical, because:

  • CVSS score 9.8: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
pipecat-aiPyPI>=0.0.41, <0.0.940.0.94
Identifiers
GHSA-c2jg-5cp7-6wc7 · CVE-2025-62373 · PYSEC-2026-458
Weakness (CWE)
CWE-502
Published
29 Jun 2026
Updated
1 Jul 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Pipecat (pipecat-ai) versions 0.0.41 up to but not including 0.0.94 are affected. The LivekitFrameSerializer class passes data received from WebSocket clients directly to pickle.loads(), so an unauthenticated remote client that can reach a server using this serializer can send a crafted pickle payload and run arbitrary code with the service's privileges. Upgrade to pipecat-ai 0.0.94 or later. Avoid using LivekitFrameSerializer, which is deprecated and not enabled by default, and bind the server to 127.0.0.1 rather than 0.0.0.0 to limit exposure.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.8 Critical 3.1 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0070, the 53rd percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.