CVE Enrichment

CVSS
9.4 CRITICAL
EPSS
0.62%
EPSS Percentile
49.69%
CISA KEV
Not listed

Description

PraisonAI is a multi-agent teams system. Prior to version 4.6.34, PraisonAI's MCP (Model Context Protocol) server (praisonai mcp serve) registers four file-handling tools by default — praisonai.rules.create, praisonai.rules.show, praisonai.rules.delete, and praisonai.workflow.show. Each accepts a path or filename string from MCP tools/call arguments and joins it onto ~/.praison/rules/ (or, for workflow.show, accepts an absolute path) with no containment check. The JSON-RPC dispatcher passes params["arguments"] blind to each handler via **kwargs without validating against the advertised input schema. By setting rule_name="../../<some-path>" an attacker walks out of the rules directory and writes any file the running user can write. Dropping a Python .pth file into the user site-packages directory escalates this primitive to arbitrary code execution in any subsequent Python process the user spawns — the next praisonai CLI invocation, an IDE script run, the user's python REPL, or any background Python service. This issue has been patched in version 4.6.34.

Technical Details

CVSS Version
4.0
CNA / NVD Source
[email protected]
Published
08-May-2026 21:16
Last Modified
17-Jun-2026 17:50
EPSS Date
2026-10-30
CWE
CWE-20, CWE-22, CWE-94, CWE-829, CWE-913

CVSS Vector

CVSS:4.0 AV:N / AC:L / AT:N / PR:N / UI:P / VC:H / VI:H / VA:H / SC:H / SI:H / SA:H / E:X / CR:X / IR:X / AR:X / MAV:X / MAC:X / MAT:X / MPR:X / MUI:X / MVC:X / MVI:X / MVA:X / MSC:X / MSI:X / MSA:X / S:X / AU:X / R:X / V:X / RE:X / U:X

Affected Products / Versions

References

Last enrichment sync: 31-Oct-2026 07:22
Sources: NVD · FIRST EPSS · CISA KEV
Latest successful provider update; providers refresh independently.

Reported Context (1)

CVE (11)

VIEW MORE

MITRE ATT&CK (4)

Products (8)

Countries (1)

Note: Related entities, including threat actors, malware, CVEs, MITRE ATT&CK techniques, vendors, products, tools, countries, and industries, are shown when they appear in the same reporting. Their presence does not necessarily mean they were targeted, compromised, vulnerable, responsible for the activity, or directly involved in the incident.