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
影響: pip:filelock >= 3.30.0, <= 4.2.0 → 4.2.1
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(). 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 di…
Read on GitHub Advisory Database
| CVE | CVE-2026-112908 |
|---|---|
| Source | GitHub Advisory Database |
| Fetched | 10/29/2026, 09:48 AM |
| Data | Markdown JSON |
On 10/29/2026, 06:09 AM, GitHub Advisory Database published "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" (type: Advisory). Severity is "Medium" (medium). Related technologies: Python. CVE: CVE-2026-112908.