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.

Project Subscriptions

Vendors Products
Tox-dev Subscribe
Filelock Subscribe
Advisories
Source ID Title
Github GHSA Github GHSA GHSA-9vhv-jxww-xfm5 filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

Fri, 06 Nov 2026 12:15:00 +0000

Type Values Removed Values Added
Weaknesses CWE-412
References
Metrics threat_severity

None

threat_severity

Low


Fri, 06 Nov 2026 00:00:00 +0000

Type Values Removed Values Added
First Time appeared Tox-dev
Tox-dev filelock
Vendors & Products Tox-dev
Tox-dev filelock

Thu, 05 Nov 2026 22:00:00 +0000

Type Values Removed Values Added
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.
Title filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database
Weaknesses CWE-367
References
Metrics cvssV3_1

{'score': 3.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L'}


Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-11-06T17:37:41.173Z

Reserved: 2026-10-19T20:16:09.858Z

Link: CVE-2026-112913

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-11-05T22:17:47.043

Modified: 2026-11-06T18:17:49.573

Link: CVE-2026-112913

cve-icon Redhat

Severity : Low

Publid Date: 2026-11-05T21:48:38Z

Links: CVE-2026-112913 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-11-06T14:00:07Z

Weaknesses