Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
3.3
CVE-2026-112913: filelock on Windows can be blocked by other users' SQLite files
CVE-2026-112913 · published 16 days ago
Summary
The filelock library (versions 3.20.4 through 4.2.0) uses SQLite files that automatically generate side files in the same folder. If another local user can create a file in that folder and then denies delete permission, the side file can cause operations to fail with disk I/O errors for the original user. Remove the unwanted side files or restrict folder permissions to prevent other users from adding files.
What to do
- Update bernát gábor filelock to version 4.2.1.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | tox-dev | filelock | >= 3.20.4, < 4.2.1 |
| pip | bernát gábor | filelock |
>= 3.20.4, <= 4.2.0 Fix: upgrade to 4.2.1
|
| Ubuntu:Pro:18.04:LTS | canonical | python-filelock | All versions |
Original advisory text
filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database
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.
References
- https://github.com/tox-dev/filelock/pull/834 Patch
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81c... Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1
- https://github.com/advisories/GHSA-9vhv-jxww-xfm5
- https://github.com/tox-dev/filelock/pull/854 Patch
- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778... Patch
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/112xxx/CVE-2026-1129... Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2026-112913 Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5 Vendor Advisory
- https://ubuntu.com/security/CVE-2026-112913 Third Party Advisory
- https://www.cve.org/CVERecord?id=CVE-2026-112913 Third Party Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-367Time-of-check Time-of-use (TOCTOU) Race Condition
Timeline
Published5 Nov 2026
Updated22 Nov 2026
First seen23 Oct 2026
Sources
GHSA-9vhv-jxww-xfm5 · GHSA
CVE-2026-112913 · NVD
CVE-2026-112913 · MITRE
CVE-2026-112913 · OSV
UBUNTU-CVE-2026-112913 · OSV
Track software like this
Free during beta