A path traversal vulnerability in the "revision" command allowed a crafted migration name supplied via the "-m" argument to escape the intended migrations directory. Under specific conditions, an attacker could cause the tool to create a ".sql" file in an arbitrary location writable by the user executing the command. This issue is only exploitable if an attacker can influence the migration name passed to the "revision" command, such as through an insecure automation or CI/CD pipeline that forwards untrusted input.