SB2026110260 - Multiple vulnerabilities in filelock
Published: November 2, 2026
Breakdown by Severity
- Low
- Medium
- High
- Critical
Description
This security bulletin contains information about 17 vulnerabilities.
1) Race Condition Enabling Link Following (CVE-ID: CVE-2026-112914)
CWE-ID: CWE-363 - Race Condition Enabling Link Following
CVSSv4: 5.8 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to disclose another user's file metadata and enable modification or truncation of that file through subsequent operations by the lock user.
The vulnerability exists due to a race condition enabling symbolic link following in filelock's break_lock_file() restore branch when restoring a live soft-lock marker on runtimes where os.link follows symbolic links. A local user can manipulate a stale marker and replace the renamed break file with a symbolic link between lstat and os.link in a writable shared lock directory without the sticky bit to create a hard link to a file owned by the lock user, expose its metadata, and redirect subsequent file operations by that user to the linked file.
The target file and lock directory must be on the same filesystem, and the lock user must take the lock more than once.
2) Insufficient verification of data authenticity (CVE-ID: CVE-2026-112939)
CWE-ID: CWE-345 - Insufficient Verification of Data Authenticity
CVSSv4: 5.7 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to bypass mutual exclusion and compromise the integrity of data protected by a soft lock through concurrent writes.
The vulnerability exists due to insufficient verification of data authenticity in filelock's soft-lock stale-owner detection when evaluating owner records in writable marker files. A local user can overwrite a live holder's marker with a dead process ID, despite lacking permission to remove the marker, to induce a contender running as the holder's account or root to remove it and acquire the lock while the original holder remains in the critical section.
3) Use of multiple resources with duplicate identifier (CVE-ID: CVE-2026-112906)
CWE-ID: CWE-694 - Use of Multiple Resources with Duplicate Identifier
CVSSv4: 5.7 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to undermine mutual exclusion and compromise the integrity of data protected by another user's file locks or leases.
The vulnerability exists due to use of duplicate file identifiers in filelock's SoftFileLock, MarkerSoftFileLock, and SoftFileLease when tracking marker age using only modification time and inode number. A local user can create an empty file in a shared lock directory, set its modification time to a future clock tick, and unlink it at that tick so a newly created marker with the same inode and timestamp inherits the previous file's watched age. Waiting processes can consequently remove a live lock or prematurely expire a live lease, allowing concurrent access to protected data.
4) Race Condition Enabling Link Following (CVE-ID: CVE-2026-112940)
CWE-ID: CWE-363 - Race Condition Enabling Link Following
CVSSv4: 6.9 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a local user to overwrite, create, or delete files with the lock user's privileges, bypass reader/writer lock exclusion, or cause a denial of service.
The vulnerability exists due to a race condition enabling link following and unsafe handling of SQLite side files in ReadWriteLock and AsyncReadWriteLock when opening lock databases in directories where another account can create or rename entries. A local user can plant symlinks or crafted SQLite journal, WAL, and shared-memory files to redirect database access, trigger journal recovery, or disrupt locking to modify or delete the lock user's files, bypass lock exclusion, or cause lock acquisition failures and process termination.
Windows does not use the vulnerable code path.
5) Unverified Ownership (CVE-ID: CVE-2026-112911)
CWE-ID: CWE-283 - Unverified Ownership
CVSSv4: 5.8 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N]
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.
6) Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-ID: CVE-2026-112941)
CWE-ID: CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
CVSSv4: 4.8 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to create, overwrite, and delete files with lock-protocol names in directories writable by another user running the lock.
The vulnerability exists due to a time-of-check time-of-use gap in the directory validation performed by SoftReadWriteLock and AsyncSoftReadWriteLock when reusing a previously validated lock tree. A local user can replace a controllable lock tree or its subdirectories with symbolic links after validation to redirect subsequent file creation, replacement, and deletion operations into directories writable by the lock-running user.
Written content is limited to filelock's own lock records rather than user-selected bytes.
7) Use of Incorrectly-Resolved Name or Reference (CVE-ID: CVE-2026-112909)
CWE-ID: CWE-706 - Use of Incorrectly-Resolved Name or Reference
CVSSv4: 6.9 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:N/SC:N/SI:N/SA:N]
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.
8) Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-ID: CVE-2026-112937)
CWE-ID: CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
CVSSv4: 6.9 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N]
The vulnerability allows a local user to delete another user's directory trees with that user's permissions and cause a limited denial of service.
The vulnerability exists due to a time-of-check time-of-use weakness in filelock's ReadWriteLock and AsyncReadWriteLock when recursively deleting private hard-link directories without verifying their identity. A local user can rename eligible directories onto remembered .filelock-* paths or forge dead-owner directory names in a writable shared parent to trigger deletion with the lock user's permissions. A deeply nested forged directory can also cause initial lock construction to fail on Python 3.11.
9) Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-ID: CVE-2026-112935)
CWE-ID: CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
CVSSv4: 5.7 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to bypass mutual exclusion and compromise the integrity of data protected by a file lock by causing two processes to hold the same lock simultaneously.
The vulnerability exists due to a time-of-check time-of-use race condition in filelock's break_lock_file stale-lock handling when checking a marker's inode number and modification time after closing its file descriptor. A local user can create a stale marker in a writable lock directory, set its modification time into the future, and unlink it after a contender reads it, causing a successor's live marker with the reused inode number to be deleted and allowing concurrent access to protected data.
Exploitation requires a filesystem with immediate inode-number reuse, such as ext4 or xfs, and at least two contending processes belonging to the lock user.
10) Time-of-check Time-of-use (TOCTOU) Race Condition (CVE-ID: CVE-2026-112913)
CWE-ID: CWE-367 - Time-of-check Time-of-use (TOCTOU) Race Condition
CVSSv4: 4.8 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N]
The vulnerability allows a local user to cause a denial of service by preventing reader and writer lock acquisition.
The vulnerability exists due to insufficient validation of SQLite side files in the Windows _connect implementation used by ReadWriteLock and AsyncReadWriteLock when opening a lock database in a directory writable by another account. A local user can place a non-empty <database>-wal file beside the database and deny deletion through its access control list to make every lock acquisition fail immediately with sqlite3.OperationalError instead of observing the configured timeout.
11) Resource exhaustion (CVE-ID: CVE-2026-112915)
CWE-ID: CWE-400 - Resource exhaustion
CVSSv4: 6.8 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a local user to cause a denial of service by making lock acquisition consume excessive memory or CPU and stall or hang regardless of configured timeouts.
The vulnerability exists due to uncontrolled resource consumption in filelock's ReadWriteLock and AsyncReadWriteLock when loading the schema of a supplied SQLite lock database during acquisition. A local user can create or overwrite a writable lock database with crafted schema records or repeatedly referenced database pages to cause prolonged or effectively unending schema processing. The PRAGMA journal_mode=MEMORY statement triggers schema loading, which is not bounded by SQLite's busy_timeout, so timeout and blocking=False do not limit the operation.
The process acquiring the lock must be able to open the supplied database file for both reading and writing.
12) Incorrect permission assignment for critical resource (CVE-ID: CVE-2026-112910)
CWE-ID: CWE-732 - Incorrect Permission Assignment for Critical Resource
CVSSv4: 4.8 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N]
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.
13) Link following (CVE-ID: CVE-2026-112912)
CWE-ID: CWE-59 - Improper Link Resolution Before File Access ('Link Following')
CVSSv4: 2 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N]
The vulnerability allows a local user to disclose whether a chosen path exists and is writable by the user acquiring a lock, including paths inside directories inaccessible to the probing user.
The vulnerability exists due to improper symbolic link resolution and a time-of-check/time-of-use race in filelock's raise_on_not_writable_file() helper when checking a soft lock path with os.lstat() followed by os.access(). A local user can create entries in the lock directory and repeatedly swap a mode-0466 file with a symlink to a chosen target between these checks, then distinguish PermissionError from the ordinary lock timeout to infer whether the target exists and is writable by the lock user.
14) Incorrect permission assignment for critical resource (CVE-ID: CVE-2026-112908)
CWE-ID: CWE-732 - Incorrect Permission Assignment for Critical Resource
CVSSv4: 5.8 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N]
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.
15) Race Condition Enabling Link Following (CVE-ID: CVE-2026-112938)
CWE-ID: CWE-363 - Race Condition Enabling Link Following
CVSSv4: 5.8 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a local user to create directories and claim files with another user's privileges in unintended locations, disclose limited directory information, cause a denial of service, and bypass another strict lock's mutual exclusion.
The vulnerability exists due to a race condition enabling symbolic link following in filelock's StrictSoftFileLock and AsyncStrictSoftFileLock when resolving claim-directory paths after checking the coordination directory. A local user can replace a renameable <path>.filelock directory with a symbolic link between the check and subsequent pathname operations to redirect claim creation into a directory writable by the lock user's process and strand claims that block another lock. The claims property and force_break() also follow unchecked paths without requiring a race, permitting directory-information disclosure through exposed errors or removal of another lock's live claims during blind recovery.
16) UNIX Hard Link (CVE-ID: CVE-2026-112934)
CWE-ID: CWE-62 - UNIX Hard Link
CVSSv4: 6.9 [CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N]
The vulnerability allows a local user to cause a denial of service, disrupt lock exclusivity, and conditionally corrupt files writable by the locking process.
The vulnerability exists due to improper validation of reopened file types and identities in the holder-record refresh mechanism used by SoftReadWriteLock and AsyncSoftReadWriteLock when refreshing records during acquisition polling or heartbeats. A local user can rename a FIFO or hard link over a holder record in a lock tree they control to block acquisition beyond its timeout, stall heartbeats without notifying the holder of eviction, or overwrite the beginning of a target file with holder-record data.
The hard-link variant additionally requires a kernel policy that permits creating hard links to files owned by another user.
17) Improper locking (CVE-ID: CVE-2026-112907)
CWE-ID: CWE-667 - Improper Locking
CVSSv4: 2 [CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N]
The vulnerability allows a local user to cause a denial of service by delaying soft-lock acquisition beyond configured timeouts and preventing stale-lock removal on Windows.
The vulnerability exists due to improper locking in filelock's soft-lock marker handling on Windows when opening, renaming or deleting an existing marker by path. A local user can obtain a Level 1 opportunistic lock on a readable marker while no other handle is open and leave break requests unanswered to block marker operations beyond the acquisition timeout, bypass cancellation checks and prevent stale-lock removal.
Remediation
Install update from vendor's website.
References
- https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh
- https://github.com/tox-dev/filelock/security/advisories/GHSA-rfpc-qcw5-3pc4
- https://github.com/tox-dev/filelock/security/advisories/GHSA-2g95-wg33-c5x2
- https://github.com/tox-dev/filelock/security/advisories/GHSA-v4x8-3wr5-3wq8
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9c4x-gm8v-wgc4
- https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m
- https://github.com/tox-dev/filelock/security/advisories/GHSA-69hj-f68j-2879
- https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fq56-3cx3-fjxp
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5
- https://github.com/tox-dev/filelock/security/advisories/GHSA-cwqr-hh33-gh44
- https://github.com/tox-dev/filelock/security/advisories/GHSA-8mx5-7m5m-r77g
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9j6q-wvj5-jgjg
- https://github.com/tox-dev/filelock/security/advisories/GHSA-6627-m3xw-93mp
- https://github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845
- https://github.com/tox-dev/filelock/security/advisories/GHSA-567q-5qvw-pf92
- https://github.com/tox-dev/filelock/commit/e35c3af