Unverified Ownership in filelock - CVE-2026-112911
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to bypass mutual exclusion, cause unauthorized file modifications with the lock user's privileges, and cause a denial of service.
The vulnerability exists due to unverified ownership of protocol directories in filelock's strict and soft read-write lock implementations when adopting an existing directory created before the lock user's first acquisition. A local user can pre-create the protocol directory in a shared writable location and manipulate lock records to admit simultaneous holders without reporting compromise; for soft read-write locks, manipulating the directory tree can also redirect file operations into directories writable by the lock user or exhaust CPU and memory resources.
Redirected writes contain filelock's own records rather than attacker-chosen content.