Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
CVE-2026-68549: ClickMigrate may write files outside its migration folder
CVE-2026-68549 · published 2 days ago
Summary
ClickMigrate versions before 1.0.3 let a specially crafted migration name be used with the "revision -m" option to place a .sql file anywhere the user can write. This could happen if an automation script or CI pipeline passes untrusted input to the command. Upgrade to version 1.0.3 or later, or restrict the command to trusted users and validate migration names before running it.
What to do
- Update ivo theis clickmigrate to version 1.0.3.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| pip | ivo theis | clickmigrate |
< 1.0.3 Fix: upgrade to 1.0.3
|
Original advisory text
ClickMigrate has Path Traversal in "revision -m" argument
### Impact
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.
### Patches
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.
### Workarounds
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.
### References
- Fix commit: https://github.com/QueueForge/ClickMigrate/commit/6b1f2c0202630a82252b3331aa57e64327e112b6
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.
### Patches
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.
### Workarounds
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.
### References
- Fix commit: https://github.com/QueueForge/ClickMigrate/commit/6b1f2c0202630a82252b3331aa57e64327e112b6
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit (estimated)
- Gives an attacker partial control (estimated)
Type
CWE-22Path Traversal
Timeline
Published16 Oct 2026
Updated16 Oct 2026
First seen16 Oct 2026
Track software like this
Free during beta