tox-dev filelock

• CVE-2026-112908 Medium 5.3 filelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live hold 0.1%
• CVE-2026-112938 Medium 5.8 filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses 0.1%
• CVE-2026-112907 Low 2.5 filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break 0.1%
• CVE-2026-112913 Low 3.3 filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database 0.1%
• CVE-2026-112910 Medium 5.3 filelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACL 0.2%
• CVE-2026-112941 Low 3.3 filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock 0.1%
• CVE-2026-112940 High 7.1 filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files 0.2%
• CVE-2026-112939 Medium 4.7 filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker 0.1%
• CVE-2026-112937 Medium 6.1 filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name 0.2%
• CVE-2026-112936 Medium 6.1 filelock: ReadWriteLock follows a symlink at the lock path into SQLite 0.2%
• CVE-2026-112935 Medium 4.7 filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders 0.1%
• CVE-2026-112934 Medium 6.1 filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record 0.2%
• CVE-2026-112915 Medium 5.5 filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout 0.2%
• CVE-2026-112914 Medium 5.3 filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory 0.2%
• CVE-2026-112912 Low 2.5 filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker 0.2%
• CVE-2026-112911 Medium 6.3 filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion 0.1%
• CVE-2026-112909 Medium 6.1 filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path 0.2%
• CVE-2026-112906 Medium 4.7 filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse 0.2%
• CVE-2026-22701 Medium 5.3 filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock 0.1%
• CVE-2025-68146 Medium 6.3 filelock has TOCTOU race condition that allows symlink attacks during lock file creation 0.2%