CVE-2026-112909
filelock is a platform-independent file lock for Python
- Risk score
- 47/100
- CVSS
- 6.1 v3.1
- Exploit chance (30 days)
- 0.1%
- Published
- 20 Oct 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 …
- Affected
- See advisory
- Fix
- Upgrade the product to 4.2.1 or later.
- Exploitation
- No known exploitation
Why it is Yellow
- CVSS 6.1 medium
- On your watchlist: python
References
- https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
- https://github.com/tox-dev/filelock/pull/835
- https://github.com/tox-dev/filelock/releases/tag/4.2.1
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879
Original 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.
Last activity 20 Oct 2026. Patch Forecast updates every hour.