GHSA-9c4x-gm8v-wgc4 · published 20 Oct 2026 · updated 28 Oct 2026
filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion
6.3MediumCVSS 6.3EPSS 0%
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in filelock 4.2.1.
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.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| tox-dev | >=3.30.0 <4.2.1 | ||
| pypi: filelock | >=3.30.0 <=4.2.0 | 4.2.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in filelock (PyPI), strongest first
Embed
A live severity badge for an advisory, README or ticket