CVE-2026-112914
From 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a…
Does this matter?
Lower severity and a low EPSS score (0.16%). Track it; it rarely justifies an emergency change on its own.
Description
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. This issue is fixed in version 4.2.1.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
- EPSS
- 0.16% probability · 5th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-363, CWE-59
- Affected
- tox-dev/filelock
- Source
- security-advisories@github.com
EPSS moved from 0.1% on 21 October 2026 to 0.2% on 26 October 2026.
References
- https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4d62bPatch
- https://github.com/tox-dev/filelock/pull/843Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jhExploit, Mitigation, Patch, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.