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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4d62b Patch
- https://github.com/tox-dev/filelock/pull/843 Patch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh Exploit, Mitigation, Patch, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 9
- CwesCWE-363 → CWE-363, CWE-59NVD modified 2026-10-21 21:17
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-21 21:17
- StatusPublished → AnalyzedNVD modified 2026-10-21 21:17
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-21 15:55
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-21 16:17
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-20 14:26
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-20 19:50
- StatusReceived → PublishedNVD modified 2026-10-20 14:26
- First seenCVSS 5.3NVD modified 2026-10-20 15:17
Affected (CPE criteria) 1
cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*
References 4
- https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4d62b Patch
- https://github.com/tox-dev/filelock/pull/843 Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh Exploit, Mitigation, Patch, Vendor Advisory