CVE-2026-112906 filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...

CVE-2026-112906 filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...

CVE-2026-112906 filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuse

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...

atsfill (>=0.0.4.dev96, <=0.0.8.dev229), gam7 (7.50.0) +2 more potentially affected by CVE-2026-112906 via filelock (>=4.1.1, <=4.2.0)

filelock PYPI version =4.1.1, =0.0.4.dev96, =0.2.1, =0.2.2 Source cves: CVE-2026-112906 Source advisory: MEND:CVE-2026-112906...

CVE-2026-112906

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...

CVE-2026-112906

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the...

CVE-2026-112906

The filelock Python library (versions 4.1.0 through 4.2.1 ) is vulnerable to a flaw in SoftFileLock where it may reuse a stale observation from another local user's file through inode reuse . If an attacker pre-dates and removes their own marker, and specific conditions regarding modification tim...

PT-2026-118393

Name of the Vulnerable Software and Affected Versions filelock versions 3.32.6 through 4.2.0 Description SoftFileLock can follow a swapped symbolic link during the conditional os.access writability check for a node without its owner-write bit. This allows a local user, on specific platform and...

PT-2026-118399

Name of the Vulnerable Software and Affected Versions filelock versions 4.1.0 through 4.2.0 Description The ReadWriteLock function can remove a randomized .filelock- private-hard-link directory during cleanup. This allows a local user with rename access in a non-sticky parent directory to observe...

PT-2026-118396

Name of the Vulnerable Software and Affected Versions filelock versions 4.0.0 through 4.2.0 Description The SoftReadWriteLock function refreshes holder records by name. This behavior allows a local user with rename access to the lock directory to replace a record with a named pipe, which can stal...

PT-2026-118397

Name of the Vulnerable Software and Affected Versions filelock versions 3.22.0 through 4.2.0 Description In the SoftFileLock implementation, a race condition exists where a stale marker can be broken. This occurs if an attacker frees their own marker after a stale read, and a legitimate contender...

PT-2026-118395

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.2.0 Description The ReadWriteLock component can open a specially crafted SQLite lock database without bounding schema and query work. This allows a local user who can replace the database to cause the...

PT-2026-118385

Name of the Vulnerable Software and Affected Versions filelock versions prior to 4.2.1 Description In UnixFileLock, a regular file renamed onto the lock path can be truncated if another local user possesses rename permissions or if the file is hard-linked under a permissive hard-link policy...

PT-2026-118394

Name of the Vulnerable Software and Affected Versions filelock versions 4.1.0 through 4.2.0 Description In the SoftFileLock component, the software can restore a stale marker by name after moving it aside. This allows a local user with rename access in a non-sticky lock directory to replace the...

PT-2026-118402

Name of the Vulnerable Software and Affected Versions filelock versions 4.1.0 through 4.2.0 Description SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the .rw lock tree and resolve its names again during later record operations. This behavior allows a local user to repla...

PT-2026-118392

Name of the Vulnerable Software and Affected Versions filelock versions 3.30.0 through 4.2.0 Description StrictSoftFileLock and SoftReadWriteLock can adopt a protocol directory created by another local user within a shared parent directory. This allows the other user to modify the protocol state...

PT-2026-118400

Name of the Vulnerable Software and Affected Versions filelock versions 3.22.0 through 4.2.0 Description SoftFileLock trusts a forged process identifier within a marker. An attacker who can modify but not remove this marker can cause an authorized contender, such as root or another process under...

PT-2026-118398

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.0.8 Description The ReadWriteLock and AsyncReadWriteLock functions resolve the lock path and pass it to SQLite without rejecting a final symbolic link. This allows a local user with permissions to create name...

PT-2026-118401

Name of the Vulnerable Software and Affected Versions filelock versions 3.20.4 through 4.2.0 Description The ReadWriteLock allows SQLite to reopen the database and side files by name. On POSIX systems, an attacker with rename access in a non-sticky parent directory can swap these names to trigger...

PT-2026-118384

Name of the Vulnerable Software and Affected Versions filelock versions 4.1.0 through 4.2.0 Description In the SoftFileLock implementation, a stale observation can be reused. This occurs when an attacker pre-dates and removes their own marker while at least two lock-user processes are waiting. If...