CVE-2026-112907
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, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. 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-567q-5qvw-pf92
- github.com/tox-dev/filelock/pull/835
- github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/advisories/GHSA-567q-5qvw-pf92
- github.com/tox-dev/filelock/commit/97d694a9a3ee1721d6c79a480174dfd9b060a080
- nvd.nist.gov/vuln/detail/CVE-2026-112907
- cve.org/CVERecord?id=CVE-2026-112907
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.