CVE-2026-112906
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, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. 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/releases/tag/4.2.1
- github.com/tox-dev/filelock/security/advisories/GHSA-2g95-wg33-c5x2
- nvd.nist.gov/vuln/detail/CVE-2026-112906
- github.com/tox-dev/filelock/pull/843
- github.com/advisories/GHSA-2g95-wg33-c5x2
- nvd.nist.gov/vuln/detail/CVE-2026-112906
- cve.org/CVERecord?id=CVE-2026-112906
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.