Mend.io Vulnerability Database
The largest open source vulnerability database
What is a Vulnerability ID?
New vulnerability? Tell us about it!
CVE-2026-112938
Published:November 05, 2026
Updated:November 16, 2026
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1.
Affected Packages
filelock (CONDA):
Affected version(s) >=3.30.0 <4.2.1
Fix Suggestion:
Update to version 4.2.1
filelock (CONDA):
Affected version(s) >=3.30.0 <4.2.1
Fix Suggestion:
Update to version 4.2.1
https://github.com/tox-dev/filelock.git (GITHUB):
Affected version(s) >=4.0.0 <4.2.1
Fix Suggestion:
Update to version 4.2.1
filelock (PYTHON):
Affected version(s) >=3.30.0 <4.2.1
Fix Suggestion:
Update to version 4.2.1
filelock (PYTHON):
Affected version(s) >=3.30.0 <4.2.1
Fix Suggestion:
Update to version 4.2.1
Do you need more information?
Contact Us
CVSS v4
Base Score:
5.8
Attack Vector
LOCAL
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
LOW
Vulnerable System Integrity
LOW
Vulnerable System Availability
HIGH
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
5.8
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
LOW
Availability
HIGH
Weakness Type (CWE)
Race Condition Enabling Link Following
EPSS
Base Score:
0.11