Medium severity · published Oct 20, 2026
CVE-2026-112934
filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record
6.1
CVSS
0.2%
EPSS
No
On KEV
Description
filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1.
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Confidentiality
None
Integrity
Low
Availability
High
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 14% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FI
filelock · tox-dev
>= 4.0.0, < 4.2.1 · source: vendor, NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-112934
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-112934
Patch
https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
Patch
https://github.com/tox-dev/filelock/pull/842
Release Notes
https://github.com/tox-dev/filelock/releases/tag/4.2.1
Exploit
https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845
More from filelock
7.1
CVE-2026-112940
filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files
6.5
CVE-2025-68146
filelock has TOCTOU race condition that allows symlink attacks during lock file creation
6.3
CVE-2026-112911
filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion
6.1
CVE-2026-112937
filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name
6.1
CVE-2026-112936
filelock: ReadWriteLock follows a symlink at the lock path into SQLite