https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 11 Nov 2026 08:37:31 +0000 https://db.gcve.eu/vuln/cve-2026-112908 <p><strong>Affected:</strong> tox-dev filelock</p> <p>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 default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1.</p> <p><strong>Affected:</strong> tox-dev filelock</p> <p>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 default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1.</p> https://db.gcve.eu/vuln/cve-2026-112908 https://db.gcve.eu/vuln/ghsa-6627-m3xw-93mp <p><strong>Affected:</strong> PyPI: filelock</p> <p>`StrictSoftFileLock` and `AsyncStrictSoftFileLock` apply the caller&#39;s `mode` to the sentinel (the lock file at `&lt;path&gt;`) 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, `&lt;path&gt;.filelock` and `&lt;path&gt;.filelock/claims`, with a bare `mkdir()`. That gives `0o777` filtered through the umask (a per-process mask that removes permission bits from new files and directories) or, under a parent with a default ACL (an access control list on a directory that sets the permissions of entries created inside it), through that ACL.</p> <p>A hold consists of two claim names in that directory, which has no sticky bit (a directory flag that lets only a file&#39;s owner remove it). When the environment leaves another local user (the other user below) a write bit on the directory, that user can unlink the holder&#39;s `0600` claims. Three settings do this: umask `000` in a sticky directory such as `/tmp`, umask `002` with the other user in the directory&#39;s group, or a default ACL on the lock&#39;s parent that grants the group write (the kernel then ignores the umask). After the unlink, the next contender of the holder&#39;s account finds the directory empty and enters. The first holder keeps reporting `is_locked == True` and later releases with no error. Affected versions: filelock &gt;= 3.30.0 and &lt;= 4.2.0 (finding `ANT-2026-AD6SUOON`).</p> <p>## Severity</p> <p>**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L, 5.3 (Medium).**</p> <p>`AV:L` (local…</p> <p><strong>Affected:</strong> PyPI: filelock</p> <p>`StrictSoftFileLock` and `AsyncStrictSoftFileLock` apply the caller&#39;s `mode` to the sentinel (the lock file at `&lt;path&gt;`) 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, `&lt;path&gt;.filelock` and `&lt;path&gt;.filelock/claims`, with a bare `mkdir()`. That gives `0o777` filtered through the umask (a per-process mask that removes permission bits from new files and directories) or, under a parent with a default ACL (an access control list on a directory that sets the permissions of entries created inside it), through that ACL.</p> <p>A hold consists of two claim names in that directory, which has no sticky bit (a directory flag that lets only a file&#39;s owner remove it). When the environment leaves another local user (the other user below) a write bit on the directory, that user can unlink the holder&#39;s `0600` claims. Three settings do this: umask `000` in a sticky directory such as `/tmp`, umask `002` with the other user in the directory&#39;s group, or a default ACL on the lock&#39;s parent that grants the group write (the kernel then ignores the umask). After the unlink, the next contender of the holder&#39;s account finds the directory empty and enters. The first holder keeps reporting `is_locked == True` and later releases with no error. Affected versions: filelock &gt;= 3.30.0 and &lt;= 4.2.0 (finding `ANT-2026-AD6SUOON`).</p> <p>## Severity</p> <p>**CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L, 5.3 (Medium).**</p> <p>`AV:L` (local…</p> https://db.gcve.eu/vuln/ghsa-6627-m3xw-93mp