Incorrect permission assignment for critical resource in filelock - CVE-2026-112910
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to disclose lock metadata, corrupt lock state, and cause a denial of service by delaying or preventing lock acquisition.
The vulnerability exists due to incorrect permission assignment in filelock's Windows file creation helper, _open_non_reparse_fd, when creating lock files and ReadWriteLock databases without enforcing the requested mode through a security descriptor. A local user can open these files where inherited directory permissions grant access, read holder metadata left in preserved lock files, modify lock state where write access is inherited, or hold byte-range locks to make subsequent acquire() calls wait or time out.
The effects are limited to the lock file or lock database; mutual exclusion between processes that follow the locking protocol remains intact.