CVE-2026-112913
filelock is a platform-independent file lock for Python. From …
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5
- github.com/tox-dev/filelock/pull/834
- github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/advisories/GHSA-9vhv-jxww-xfm5
- github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b
- github.com/tox-dev/filelock/pull/854
- nvd.nist.gov/vuln/detail/CVE-2026-112913
- cve.org/CVERecord?id=CVE-2026-112913
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.