CVE-2026-112910filelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACL
filelock is a platform-independent file lock for Python. From 3.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory's inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. This issue is fixed in version 4.2.1.
Overview
Severity
| Score | Severity | Version | Vector String |
|---|---|---|---|
| 5.3 | MEDIUM | 3.1GitHub_M (CNA) | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Details
- CVE ID
- CVE-2026-112910
- Status
- Awaiting Analysis
- Assigner (CNA)
- GitHub_M
- Published
- Nov 5, 2026
- Last modified
- 2026-11-06 21:40 UTC
- Weaknesses
- CWE-732 · Incorrect Permission Assignment for Critical Resource
Affected Products
As published by the CNA in the CVE record.
tox-devfilelock1 version range
- >= 3.10.0, < 4.2.1
References
- github.com https://github.com/tox-dev/filelock/commit/72786d41aa25159ad28c1bcf4291738b135b2c6c
- github.com https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
- github.com https://github.com/tox-dev/filelock/pull/835
- github.com https://github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com https://github.com/tox-dev/filelock/security/advisories/GHSA-8mx5-7m5m-r77g