« Volver al listado

CVE-2025-62373

Estado: AnalizadaCrítica (9.8)—

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.

Leer descripción completaMostrar menos

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.

CVSS

Probabilidad de explotación (EPSS)

EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).

🎯 Técnicas ATT&CK

Cómo se explota esta vulnerabilidad y qué consigue el atacante, en el lenguaje de MITRE ATT&CK.

Aplicación web expuesta (AV:N/AC:L/PR:N) con RCE mediante pickle.loads() en endpoint WebSocket sin validación. Ejecución de código arbitrario confirmada.

Inferido por nuestro agente de análisis a partir de la descripción oficial, el vector CVSS y la CWE, y comprobado por un supervisor. Puede contener errores.

🛡️ Mitigaciones ATT&CK que cubren estas técnicas

Tecnologías afectadas (1)

CWE

Referencias

JSON original (NVD)

Mostrar
{
  "id": "CVE-2025-62373",
  "cveTags": [],
  "metrics": {
    "ssvcV203": [
      {
        "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
        "ssvcData": {
          "id": "CVE-2025-62373",
          "role": "CISA Coordinator",
          "options": [
            {
              "exploitation": "poc"
            },
            {
              "automatable": "yes"
            },
            {
              "technicalImpact": "total"
            }
          ],
          "version": "2.0.3",
          "timestamp": "2026-04-23T18:35:31.387759Z"
        }
      }
    ],
    "cvssMetricV31": [
      {
        "type": "Secondary",
        "source": "security-advisories@github.com",
        "cvssData": {
          "scope": "UNCHANGED",
          "version": "3.1",
          "baseScore": 9.8,
          "attackVector": "NETWORK",
          "baseSeverity": "CRITICAL",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
          "integrityImpact": "HIGH",
          "userInteraction": "NONE",
          "attackComplexity": "LOW",
          "availabilityImpact": "HIGH",
          "privilegesRequired": "NONE",
          "confidentialityImpact": "HIGH"
        },
        "impactScore": 5.9,
        "exploitabilityScore": 3.9
      }
    ]
  },
  "affected": [
    {
      "source": "security-advisories@github.com",
      "affectedData": [
        {
          "vendor": "pipecat-ai",
          "product": "pipecat",
          "versions": [
            {
              "status": "affected",
              "version": ">= 0.0.41, < 0.0.94"
            }
          ]
        }
      ]
    }
  ],
  "published": "2026-04-23T16:16:24.140",
  "references": [
    {
      "url": "https://github.com/pipecat-ai/pipecat/security/advisories/GHSA-c2jg-5cp7-6wc7",
      "tags": [
        "Exploit",
        "Mitigation",
        "Vendor Advisory"
      ],
      "source": "security-advisories@github.com"
    },
    {
      "url": "https://github.com/pipecat-ai/pipecat/security/advisories/GHSA-c2jg-5cp7-6wc7",
      "tags": [
        "Exploit",
        "Mitigation",
        "Vendor Advisory"
      ],
      "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0"
    }
  ],
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "type": "Secondary",
      "source": "security-advisories@github.com",
      "description": [
        {
          "lang": "en",
          "value": "CWE-502"
        }
      ]
    }
  ],
  "descriptions": [
    {
      "lang": "en",
      "value": "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."
    },
    {
      "lang": "es",
      "value": "Pipecat es un framework Python de código abierto para construir agentes conversacionales multimodales y de voz en tiempo real. Las versiones 0.0.41 a 0.0.93 tienen una vulnerabilidad en 'LivekitFrameSerializer', una clase de serializador de frames opcional, no predeterminada e indocumentada (ahora obsoleta) destinada a la integración con LiveKit. El método 'deserialize()' de la clase utiliza 'pickle.loads()' de Python en los datos recibidos de los clientes WebSocket sin ninguna validación o sanitización. Esto significa que un cliente WebSocket malicioso puede enviar una carga útil pickle manipulada para ejecutar código arbitrario en el servidor Pipecat. El código vulnerable reside en 'src/pipecat/serializers/livekit.py' (alrededor de la línea 73), donde los datos de mensajes WebSocket no confiables se pasan directamente a 'pickle.loads()' para la deserialización. Si un servidor Pipecat está configurado para usar LivekitFrameSerializer y está escuchando en una interfaz externa (por ejemplo, 0.0.0.0), un atacante en la red (o en internet, si el servicio está expuesto) podría lograr la ejecución remota de código (RCE) en el servidor enviando una carga útil pickle maliciosa. La versión 0.0.94 contiene una corrección. Los usuarios de Pipecat deben evitar o reemplazar la deserialización insegura y mejorar la configuración de seguridad de la red. La mejor mitigación es dejar de usar el LivekitFrameSerializer vulnerable por completo. Aquellos que requieran la funcionalidad de LiveKit deben actualizar a la última versión de Pipecat y cambiar al 'LiveKitTransport' recomendado u otro método seguro proporcionado por el framework. Además, siga siempre las prácticas de codificación segura: nunca confíe en los datos proporcionados por el cliente y evite Python pickle (o deserialización insegura similar) en los componentes orientados a la red."
    }
  ],
  "lastModified": "2026-10-05T17:10:00.237",
  "configurations": [
    {
      "nodes": [
        {
          "negate": false,
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:pipecat:pipecat:*:*:*:*:*:*:*:*",
              "vulnerable": true,
              "matchCriteriaId": "F7D53166-F5C8-48C1-96DB-51FA208D9F6B",
              "versionEndExcluding": "0.0.94",
              "versionStartIncluding": "0.0.41"
            }
          ],
          "operator": "OR"
        }
      ]
    }
  ],
  "sourceIdentifier": "security-advisories@github.com"
}