Lucene search
+L

13 matches found

RedhatCVE
RedhatCVE
•added 2026/10/20 6:58 p.m.•1 views

CVE-2026-112941

A flaw was found in filelock. The SoftReadWriteLock and AsyncSoftReadWriteLock mechanisms cache an initial directory check but resolve path names again during subsequent record operations. A local attacker can exploit this behavior by replacing the lock directory structure after its initial...

3.3CVSS5.8AI score
SaveExploits0References7
NVD
NVD
•added 2026/10/20 3:17 p.m.•2 views

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...

6.1CVSS
SaveExploits0References4
NVD
NVD
•added 2026/10/20 3:17 p.m.•4 views

CVE-2026-112941

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the .rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the...

3.3CVSS
SaveExploits0References4
NVD
NVD
•added 2026/10/20 3:17 p.m.•2 views

CVE-2026-112911

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol...

6.3CVSS
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/20 2:43 p.m.•10 views

CVE-2026-112941 filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the .rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the...

3.3CVSS
SaveExploits0References4
CVE
CVE
•added 2026/10/20 2:43 p.m.•3 views

CVE-2026-112941

The filelock Python library versions 4.1.0 through 4.2.1 are vulnerable to a Time-of-check Time-of-use (TOCTOU) race condition involving SoftReadWriteLock and AsyncSoftReadWriteLock . The vulnerability occurs because these components cache a successful check of the .rw lock tree but re-resolve na...

3.3CVSS5.9AI score
SaveExploits0References4
EUVD
EUVD
•added 2026/10/20 2:43 p.m.•3 views

EUVD-2026-105032

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the .rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the...

3.3CVSS5.9AI score
SaveExploits0References4
CVE
CVE
•added 2026/10/20 2:30 p.m.•5 views

CVE-2026-112934

The filelock Python library (versions 4.0.0 through 4.2.1 ) contains a vulnerability where the SoftReadWriteLock refreshes holder records by name. A local user with rename access to the lock directory can replace a record with a named pipe , causing the lock to hang, or link a reachable target fi...

6.1CVSS5.8AI score
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/20 2:30 p.m.•8 views

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...

6.1CVSS
SaveExploits0References4
EUVD
EUVD
•added 2026/10/20 2:30 p.m.•3 views

EUVD-2026-105023

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...

6.1CVSS5.8AI score
SaveExploits0References4
Cvelist
Cvelist
•added 2026/10/20 2:21 p.m.•6 views

CVE-2026-112911 filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol...

6.3CVSS
SaveExploits0References4
CVE
CVE
•added 2026/10/20 2:21 p.m.•5 views

CVE-2026-112911

The filelock Python library contains a vulnerability where StrictSoftFileLock (versions 3.30.0 to 4.2.1) and SoftReadWriteLock (versions 4.0.0 to 4.2.1) can adopt a protocol directory created by another local user within a shared parent directory. This allows a malicious local user to alter the p...

6.3CVSS5.7AI score
SaveExploits0References4
EUVD
EUVD
•added 2026/10/20 2:21 p.m.•3 views

EUVD-2026-105018

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol...

6.3CVSS5.7AI score
SaveExploits0References4
Rows per page
Query Builder