CVE-2026-112907
Published:November 05, 2026
Updated:November 15, 2026
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.
Affected Packages
filelock (CONDA):
Affected version(s) >=4.0.1 <4.2.1Fix Suggestion:
Update to version 4.2.1https://github.com/tox-dev/filelock.git (GITHUB):
Affected version(s) >=4.0.0 <4.2.1Fix Suggestion:
Update to version 4.2.1filelock (PYTHON):
Affected version(s) >=4.0.0 <4.2.1Fix Suggestion:
Update to version 4.2.1filelock (PYTHON):
Affected version(s) >=3.22.0 <4.2.1Fix Suggestion:
Update to version 4.2.1Related ResourcesĀ (8)
Do you need more information?
Contact UsCVSS v4
Base Score:
2
Attack Vector
LOCAL
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
NONE
Vulnerable System Availability
LOW
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
2.5
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Weakness Type (CWE)
Improper Locking
EPSS
Base Score:
0.10