filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. 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/839 Patch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4 Exploit, Mitigation, Patch, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4 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 7
- StatusAnalyzed → ModifiedNVD modified 2026-10-28 16:17
- Cpes+1 CPE criteria (now 1)NVD modified 2026-10-21 21:21
- StatusPublished → AnalyzedNVD modified 2026-10-21 21:21
- StatusUndergoing Analysis → PublishedNVD modified 2026-10-20 14:21
- StatusPublished → Undergoing AnalysisNVD modified 2026-10-20 19:50
- StatusReceived → PublishedNVD modified 2026-10-20 14:21
- First seenCVSS 6.3NVD 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/839 Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4 Exploit, Mitigation, Patch, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4 Exploit, Mitigation, Patch, Vendor Advisory