Use of Incorrectly-Resolved Name or Reference in filelock - CVE-2026-112909
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to truncate another user's files and, when an explicit permissive lock mode is configured, read and modify data subsequently written to those files.
The vulnerability exists due to incorrect resolution of file references in filelock's UnixFileLock._finalize_locked_fd when acquiring a lock on a pre-existing regular file without verifying that it is the intended lock file. A local user can rename or hard-link a file owned by the user running the lock onto an unused lock path before the next acquire() to trigger truncation with that user's privileges and, if an explicit permissive mode is configured, permission changes that enable reading and modifying subsequently written data.