CVE-2026-112913
lowfilelock is a platform-independent file lock for Python.
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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L Affected products
Not reported by the source (unknown — not "none").
Weakness classification (CWE)
Source: NVD / CISA. “NVD-CWE-Other” and “NVD-CWE-noinfo” mean NVD could not assign a specific weakness.
Mitigation & advisories
No vendor advisory or patch reference tagged by NVD. Check the references below.
References
- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b security-advisories@github.com
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d security-advisories@github.com
- https://github.com/tox-dev/filelock/pull/834 security-advisories@github.com
- https://github.com/tox-dev/filelock/pull/854 security-advisories@github.com
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5 security-advisories@github.com
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5 134c704f-9b21-4f2e-91b3-4a467353bcc0

