filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. 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/e1e825b1992f69fb6b346dc395d5ae4893536c0a Patch
- https://github.com/tox-dev/filelock/pull/835 Patch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879 Exploit, Mitigation, Patch, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879 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-27 21:04
- StatusPublished → AnalyzedNVD modified 2026-10-27 21:04
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-22 21:25
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-22 22:18
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-20 14:16
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-20 19:50
- StatusReceived → PublishedNVD modified 2026-10-20 14:16
- 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/e1e825b1992f69fb6b346dc395d5ae4893536c0a Patch
- https://github.com/tox-dev/filelock/pull/835 Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879 Exploit, Mitigation, Patch, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879 Exploit, Mitigation, Patch, Vendor Advisory