UTC
High

PraisonAI's symlink-extraction bypass of `_safe_extractall` writes outside `dest_dir`

CVE-2026-44340 · GHSA-9q28-ghcr-c4x3 · published 2026-05-11

Severity
High
CVSS score
7.5
Chance of exploitation (EPSS)
0.43%
Fixed in
4.6.37
  • Exploitation No known exploitation
  • Automatable Yes
  • Technical impact Partial
  • CISA SSVC
What it is

Arbitrary file write with attacker-controlled content to an attacker-chosen path, on every host that processes a malicious .praison bundle through any of the three callers above. Realistic exploitation paths: A user runs praisonai recipe unpack ./ .praison after obtaining the bundle from a shared registry, a tutorial link, or direct messaging. A user runs praisonai recipe pull against a malicious or compromised registry. A registry server processes an uploaded .praison bundle (the publish path is reachable over the network if the server is exposed. per GHSA-r9x3-wx45-2v7f and GHSA-2xgv-5cv2-47vv).

What to do

Upgrade praisonai to 4.6.37 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.

Single-line fix at recipe/registry.py:178: filter="data" (introduced in Python 3.12; available as a backport on 3.8+ via the official PEP 706 reference implementation) refuses symlinks, hardlinks, device nodes, and absolute or escaping link targets, it is the canonical Python defense against this class. If you also support older Python, add an explicit guard inside the existing per-member loop before tar.extractall:

Affected
PackageRegistryAffectedFixed in
praisonaiPyPI<= 4.6.364.6.37
Downstream in the Official MCP Registry

1 registered MCP server installs an affected version today, by the dependency versions a fresh install resolves.

  • io.github.MervinPraison/praisonaipraisonai@2.3.42
See the trace →

The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.

Sources: GitHub Advisory Database, reviewed and malware advisories (CC BY 4.0, https://github.com/advisories); advisories published by Cursor (https://github.com/cursor/cursor/security/advisories); advisories published by OpenClaw (https://github.com/openclaw/openclaw/security/advisories); advisories published by vLLM (https://github.com/vllm-project/vllm/security/advisories); advisories published by Open WebUI (https://github.com/open-webui/open-webui/security/advisories); advisories published by n8n (https://github.com/n8n-io/n8n/security/advisories); advisories published by Flowise (https://github.com/FlowiseAI/Flowise/security/advisories); advisories published by Langflow (https://github.com/langflow-ai/langflow/security/advisories); advisories published by the MCP Python SDK project (https://github.com/modelcontextprotocol/python-sdk/security/advisories); advisories published by MLflow (https://github.com/mlflow/mlflow/security/advisories); CISA Known Exploited Vulnerabilities catalog (CC0). Data as of 2026-11-22. ShieldMap describes how each problem works and how to fix it; it does not publish exploit code. Report a correction to [email protected].