AgentReadyHomeAgent Listing

← Pexo

Pexo — agentic threat model

6.8AIVSS 6.8 · Medium

Pexo presents a moderate security risk primarily driven by its integration into corporate communication channels (Slack, Lark) and its orchestration of multiple third-party video generation models. While its human-in-the-loop preview mechanism mitigates some autonomous execution risks, the lack of explicit security guardrails for deepfake prevention and data privacy in chat environments remains a concern.

OWASP AIVSS score rationale

AIVSS = (CVSS_Base + AARS) × Mitigation_Factor, where AARS = (10 − CVSS_Base) × (Factor_Sum / 10) × ThM
CVSS base 6.3AARS uplift 1.67Factor sum 4.3/10Threat ×1.05Mitigation ×0.85
Autonomy of Action
0.40
Goal-Driven Planning
0.60
Self-Modification
0.10
Dynamic Tool Use
0.50
Persistent Memory
0.30
Contextual Awareness
0.50
Dynamic Identity
0.20
Multi-Agent Interactions
0.40
Non-Determinism
0.70
Opacity & Reflexivity
0.60

Scored with the canonical OWASP AIVSS formula (AIVSS calculator reference); agentic risk factors estimated from the agent’s described capabilities.

MAESTRO 7-layer threat model

Per-layer threats for this agent. Layers tagged “not certain from listing” are general, caveated commentary where the public description didn’t pin that layer.

L1 · Foundation Models✓ mapped

Pexo utilizes multi-model intelligence, dynamically selecting from third-party foundation models like Seedance, Sora, and Kling. This exposes the agent to upstream model vulnerabilities, including adversarial prompt injection that could bypass safety filters of the underlying video generation models.

L2 · Data Operations⚠ not certain from listing

Not certain from the listing — Pexo pulls references and suggests creative directions, which suggests it may query external databases or search engines. This introduces risks of data poisoning or intellectual property exfiltration if user-provided assets are ingested into training or reference pipelines.

L3 · Agent Frameworks✓ mapped

The agent framework orchestrates a non-linear workflow, managing state across scene selection, model routing, and rendering. Vulnerabilities in this orchestration layer could allow attackers to manipulate the model-selection logic or inject malicious instructions into the video generation pipeline.

L4 · Deployment & Infrastructure⚠ not certain from listing

Not certain from the listing — Pexo likely runs on cloud infrastructure to handle heavy video rendering and API orchestration. Security risks include insecure API key storage for third-party video models and potential container escape vulnerabilities during rendering tasks.

L5 · Evaluation & Observability✓ mapped

Pexo features a 'Preview Before Production' workflow, acting as a human-in-the-loop guardrail. However, there is no mention of automated content moderation or deepfake detection tools to prevent the generation of harmful or copyrighted video content.

L6 · Security & Compliance (cross-cutting)⚠ not certain from listing

Not certain from the listing — As a free, closed-source tool, there is no public evidence of compliance certifications (e.g., SOC2, GDPR) or robust access control policies governing how user data and generated videos are stored and protected.

L7 · Agent Ecosystem✓ mapped

Pexo integrates directly with enterprise messaging ecosystems like Slack, Lark, and WhatsApp. If compromised, the agent could be used as a vector for social engineering, phishing, or unauthorized data harvesting within corporate communication channels.

MAESTRO — the 7-layer agentic threat-modeling framework (Cloud Security Alliance / Ken Huang).