Incorrect permission assignment for critical resource in filelock - CVE-2026-112908
Published: November 2, 2026
Vulnerability details
The vulnerability allows a local user to bypass mutual exclusion, compromise the integrity of lock-protected data, and cause a denial of service.
The vulnerability exists due to incorrect permission assignment in filelock's _ensure_protocol_directory function when creating claim directories for StrictSoftFileLock and AsyncStrictSoftFileLock without applying the caller's restrictive mode. A local user can unlink a holder's claims if a permissive umask or inherited default ACL grants write access to those directories, allowing another process of the holder's account to acquire the lock concurrently, or plant a malformed claim file to prevent lock acquisition.