34 matches found
UBUNTU-CVE-2026-112908
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
Linux Distros Unpatched Vulnerability : CVE-2026-112908
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX system...
CVE-2026-112908
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
Linux Distros Unpatched Vulnerability : CVE-2026-112938
The Linux/Unix host has one or more packages installed that are impacted by a vulnerability without a vendor supplied patch available. - filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate th...
DEBIAN-CVE-2026-112938
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
CVE-2026-112938
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
DEBIAN-CVE-2026-112908
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
CVE-2026-112908
The filelock library for Python (versions 3.30.0 through 4.2.1) contains a vulnerability in its StrictSoftFileLock and AsyncStrictSoftFileLock components on POSIX systems. The root cause is that these components create coordination and claim directories without applying the caller’s restrictive l...
CVE-2026-112908 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
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
EUVD-2026-117817
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
CVE-2026-112908 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
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited...
CVE-2026-112938 filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
EUVD-2026-117814
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
CVE-2026-112938
The filelock Python library (versions 3.30.0 through 4.2.1 ) is vulnerable to a race condition on POSIX platforms. In StrictSoftFileLock and AsyncStrictSoftFileLock , a local account can rename a coordination name to swap in a symbolic link between the directory validation check and the subsequen...
CVE-2026-112938 filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
CVE-2026-112938: tox-dev filelock: filelock is a platform-independent file lock for Python
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in ensureprotocoldirectory but later reach the claims directory through opendirectory by pathname, allowing a...
Filelock: StrictSoftFileLock And SoftReadWriteLock Adopt A Protocol Directory Another User Created First, Losing Mutual
"StrictSoftFileLock", "AsyncStrictSoftFileLock", "SoftReadWriteLock" and "AsyncSoftReadWriteLock" keep their whole ownership state as files in a directory derived from the lock path ".filelock/claims", ".rw/gen,holders". When that directory already exists they adopt it after checking only that it...
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
StrictSoftFileLock and AsyncStrictSoftFileLock apply the caller's mode to the sentinel the lock file at and to both claim files the files whose presence says a process wants or holds the lock. They create the two directories that hold the claims, .filelock and .filelock/claims, with a bare mkdir...
GHSA-6627-M3XW-93MP 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
StrictSoftFileLock and AsyncStrictSoftFileLock apply the caller's mode to the sentinel the lock file at and to both claim files the files whose presence says a process wants or holds the lock. They create the two directories that hold the claims, .filelock and .filelock/claims, with a bare mkdir...
GHSA-9C4X-GM8V-WGC4 filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion
StrictSoftFileLock, AsyncStrictSoftFileLock, SoftReadWriteLock and AsyncSoftReadWriteLock keep their whole ownership state as files in a directory derived from the lock path .filelock/claims, .rw/gen,holders. When that directory already exists they adopt it after checking only that it is a real...