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.
Fix
Patch, vendor advisory and mitigation references on NVD 4
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03 Patch
- https://github.com/tox-dev/filelock/pull/842 Patch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845 Exploit, Mitigation, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845 Exploit, Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 7
- StatusAnalyzed → ModifiedNVD modified 2026-10-22 22:18
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-21 21:13
- StatusPublished → AnalyzedNVD modified 2026-10-21 21:13
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-20 14:30
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-20 19:50
- StatusReceived → PublishedNVD modified 2026-10-20 14:30
- First seenCVSS 6.1NVD modified 2026-10-20 15:17
Affected (CPE criteria) 1
cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*
References 5
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03 Patch
- https://github.com/tox-dev/filelock/pull/842 Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845 Exploit, Mitigation, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845 Exploit, Mitigation, Vendor Advisory