filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. 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/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d Patch
- https://github.com/tox-dev/filelock/pull/834 Patch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85 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 8
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-21 18:05
- StatusPublished → AnalyzedNVD modified 2026-10-21 18:05
- 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:36
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-20 19:50
- StatusReceived → PublishedNVD modified 2026-10-20 14:36
- First seenCVSS 6.1NVD 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/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d Patch
- https://github.com/tox-dev/filelock/pull/834 Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85 Exploit, Mitigation, Patch, Vendor Advisory