CVE-2026-112913
filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database
- Low 3.3
Description
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.
Key facts
- Published
- 5 Nov 2026
- Last changed
- 6 Nov 2026
- Assigned by
- GitHub_M
- EPSS
- 0.118% likely to be exploited in the next 30 days, higher than 1.74% of CVEs (scores for 16 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 3.3CVSS 3.1, Lowfrom the CNA (GitHub_M)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| tox-dev | filelock |
|
Timeline
- 5 Nov 2026 Published
Weakness
References
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5
- https://github.com/tox-dev/filelock/pull/834
- https://github.com/tox-dev/filelock/pull/854
- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d