CVE-2026-112941
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, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the <path>.rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the first acquisition to redirect lock-record writes into directories writable by the lock user. 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/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- github.com/tox-dev/filelock/pull/842
- github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m
- nvd.nist.gov/vuln/detail/CVE-2026-112941
- github.com/advisories/GHSA-wfhq-q4j2-c37m
- nvd.nist.gov/vuln/detail/CVE-2026-112941
- cve.org/CVERecord?id=CVE-2026-112941
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.