Live › vulnerability › CVE-2026-68549
Go to dashboardClickMigrate's revision command let a crafted migration name passed via -m escape the migrations directory. An attacker who controls that input can make the tool write a .sql file to any location the running user can write to.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:11 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| ClickMigrate | pypi | < 1.0.3 | 1.0.3 |
pip show ClickMigrate and check whether the version is below 1.0.3revision -m to see whether any untrusted input reaches it1.0.3 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
The vulnerability has been fixed in version 1.0.3 by validating and sanitizing the migration name to prevent directory traversal.
Users should upgrade to version 1.0.3 or later.
Do not pass untrusted input to the revision -m argument.
If upgrading is not immediately possible, ensure that only trusted users or automation can invoke the revision command and that migration names are validated before being passed to the tool.
This page as .md · .json · in your agent: get_signal("CVE-2026-68549")
GitHub Advisory Database, CC-BY 4.0. Posts quoted belong to their authors.