Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | >= 3.30.0, < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77Patch
- https://github.com/tox-dev/filelock/pull/839Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4ExploitMitigationPatch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4ExploitMitigationPatch
FAQ
What is CVE-2026-112911?
CVE-2026-112911 is a vulnerability with a CVSS score of 6.3 (MEDIUM). 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 creat...
How severe is CVE-2026-112911?
CVE-2026-112911 has been rated MEDIUM with a CVSS base score of 6.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112911?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.