CVE-2026-112906
Published:October 20, 2026
Updated:October 22, 2026
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.
Affected Packages
filelock (CONDA):
Affected version(s) >=4.1.0 <4.2.1Fix Suggestion:
Update to version 4.2.1https://github.com/tox-dev/filelock.git (GITHUB):
Affected version(s) >=4.1.0 <4.2.1Fix Suggestion:
Update to version 4.2.1filelock (PYTHON):
Affected version(s) >=4.1.0 <4.2.1Fix Suggestion:
Update to version 4.2.1Related Resources (3)
Do you need more information?
Contact UsCVSS v4
Base Score:
5.7
Attack Vector
LOCAL
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
LOW
User Interaction
NONE
Vulnerable System Confidentiality
NONE
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
4.7
Attack Vector
LOCAL
Attack Complexity
HIGH
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
Use of Multiple Resources with Duplicate Identifier
EPSS
Base Score:
0.21