How severe is CVE-2026-68549?

CVE-2026-68549 has a CVSS score of 3.3/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2026-68549?

CVE-2026-68549 affects the following packages: clickmigrate (PyPI). Ecosystems affected: PyPI.

How do I fix CVE-2026-68549?

Update clickmigrate to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-68549 is resolved across your whole dependency graph.

How do I detect CVE-2026-68549 in my PyPI dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clickmigrate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2026-68549 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-68549 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-68549 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was CVE-2026-68549 published, and has it been updated?

CVE-2026-68549 was published on October 16, 2026 and was last updated on October 16, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍

🐍 PyPI

Not in CISA KEV

LOW severity

CVE-2026-68549 — clickmigrate

LOWFix: QueueForge/ClickMigrate@6b1f2c0

CVE-2026-68549 is a low-severity (CVSS 3.3) vulnerability in clickmigrate. A fix is available for clickmigrate — see the affected versions and patch details below.

ClickMigrate has Path Traversal in "revision -m" argument

Published

Oct 16, 2026

Updated

Oct 16, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 16, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐍clickmigrate

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐍PyPI	`clickmigrate`	all versions	1.0.3`pip install --upgrade 'clickmigrate==1.0.3'`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for clickmigrate, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update clickmigrate to 1.0.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-68549 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Frequently Asked Questions

### 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 v

O3 Security · Impact-Aware SCA

Is CVE-2026-68549 in your dependencies?

Find it across PyPI, including transitive dependencies.

Scan my dependencies How O3 SCA works