Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | >= 4.1.0, < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81cPatch
- https://github.com/tox-dev/filelock/pull/834Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85ExploitMitigationPatch
FAQ
What is CVE-2026-112937?
CVE-2026-112937 is a vulnerability with a CVSS score of 6.1 (MEDIUM). filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local us...
How severe is CVE-2026-112937?
CVE-2026-112937 has been rated MEDIUM with a CVSS base score of 6.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112937?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.