← CVE Radar
CVE-2026-112907filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. This issue is fixed in version 4.2.1.
2.5 LOWEPSS 0.10%Not in KEVNVD: Awaiting Analysis
Overview
Severity
| Score | Severity | Version | Vector String |
|---|---|---|---|
| 2.5 | LOW | 3.1GitHub_M (CNA) | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L |
Details
- CVE ID
- CVE-2026-112907
- Status
- Awaiting Analysis
- Assigner (CNA)
- GitHub_M
- Published
- Nov 5, 2026
- Last modified
- 2026-11-06 21:40 UTC
- Weaknesses
- CWE-667 · Improper Locking
Affected Products
As published by the CNA in the CVE record.
tox-devfilelock1 version range
- >= 3.22.0, < 4.2.1
References
- github.com https://github.com/tox-dev/filelock/commit/97d694a9a3ee1721d6c79a480174dfd9b060a080
- 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-567q-5qvw-pf92