CVE-2026-112937
filelock is a platform-independent file lock for Python. From 4.1.0 …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d
- github.com/tox-dev/filelock/pull/834
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85
- nvd.nist.gov/vuln/detail/CVE-2026-112937
- github.com/advisories/GHSA-jqc4-5cvw-7w85
- nvd.nist.gov/vuln/detail/CVE-2026-112937
- cve.org/CVERecord?id=CVE-2026-112937
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.