CVE-2026-112935
filelock is a platform-independent file lock for Python. From …
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. 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/740ff666b62a88496c8d7394e4e6230605e4d62b
- github.com/tox-dev/filelock/pull/843
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/tox-dev/filelock/security/advisories/GHSA-fq56-3cx3-fjxp
- nvd.nist.gov/vuln/detail/CVE-2026-112935
- github.com/advisories/GHSA-fq56-3cx3-fjxp
- nvd.nist.gov/vuln/detail/CVE-2026-112935
- cve.org/CVERecord?id=CVE-2026-112935
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.