Vulnerability Description
filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. This issue is fixed in version 4.2.1.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536Patch
- https://github.com/tox-dev/filelock/pull/835Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879ExploitMitigationPatch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879ExploitMitigationPatch
FAQ
What is CVE-2026-112909?
CVE-2026-112909 is a vulnerability with a CVSS score of 6.1 (MEDIUM). filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or ha...
How severe is CVE-2026-112909?
CVE-2026-112909 has been rated MEDIUM with a CVSS base score of 6.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112909?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.