CVE-2026-112936

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

CVE-2026-112936

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

CVE-2026-112936 filelock: ReadWriteLock follows a symlink at the lock path into SQLite

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

gam7 (>=7.48.17, <=7.49.5), inference-core (>=1.2.7, <=1.6.0) +4 more potentially affected by CVE-2026-112936 via filelock (>=4.0.0, <=4.0.8)

filelock PYPI version =4.0.0, =7.48.17, =1.2.7, =0.3.0, =2.2.0, =3.2.4 - vulpix 2.1.0 - weblate 2026.10.0 Source cves: CVE-2026-112936 Source advisory: MEND:CVE-2026-112936...

CVE-2026-112936

The filelock Python library (versions 3.20.4 through 4.0.9 ) contains a vulnerability where ReadWriteLock and AsyncReadWriteLock resolve lock paths and pass them to SQLite without rejecting a final symbolic link. This allows a local user with the ability to create names in the lock directory to r...

CVE-2026-112936

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

CVE-2026-112936 filelock: ReadWriteLock follows a symlink at the lock path into SQLite

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

CVE-2026-112936 filelock: ReadWriteLock follows a symlink at the lock path into SQLite

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory t...

CVE-2026-112935

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

atsfill (>=0.0.4.dev96, <=0.0.8.dev229), displayrws (>=0.1.3, <=0.1.4) +16 more potentially affected by CVE-2026-112935 via filelock (>=4.0.0, <=4.2.0)

filelock PYPI version =4.0.0, =0.0.4.dev96, =0.1.3, =5.4.2, =2026.10.0b1, =0.10.43, =0.10.43, =7.48.17, =0.10.43, =1.2.7, =0.2.1, =0.3.0, =2.2.0, =0.1.0, =0.1.2 and more Source cves: CVE-2026-112935 Source advisory: MEND:CVE-2026-112935...

CVE-2026-112935 filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

CVE-2026-112935

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

CVE-2026-112935 filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

CVE-2026-112935

The filelock library, a platform-independent file lock for Python, is vulnerable to a TOCTOU Race Condition in its SoftFileLock component. In versions 3.22.0 through 4.2.0 , an attacker can free their own marker after a stale read. If an honest contender subsequently creates a live successor on a...

CVE-2026-112935

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

CVE-2026-112935 filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not...

CVE-2026-112934 filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link polic...

atsfill (>=0.0.4.dev96, <=0.0.8.dev229), displayrws (>=0.1.3, <=0.1.4) +16 more potentially affected by CVE-2026-112934 via filelock (>=4.0.0, <=4.2.0)

filelock PYPI version =4.0.0, =0.0.4.dev96, =0.1.3, =5.4.2, =2026.10.0b1, =0.10.43, =0.10.43, =7.48.17, =0.10.43, =1.2.7, =0.2.1, =0.3.0, =2.2.0, =0.1.0, =0.1.2 and more Source cves: CVE-2026-112934 Source advisory: MEND:CVE-2026-112934...

CVE-2026-112934 filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link polic...

CVE-2026-112934

filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link polic...