CVE-2026-112908
filelock is a platform-independent file lock for Python. From …
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. 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/security/advisories/GHSA-6627-m3xw-93mp
- github.com/tox-dev/filelock/pull/839
- github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/advisories/GHSA-6627-m3xw-93mp
- github.com/tox-dev/filelock/commit/8cf51802158b9cf7e1fc560c2da30491a662cfde
- nvd.nist.gov/vuln/detail/CVE-2026-112908
- cve.org/CVERecord?id=CVE-2026-112908
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.