filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

影響: pip:filelock >= 4.1.0, <= 4.2.0 → 4.2.1

ReadWriteLock and AsyncReadWriteLock (the SQLite-backed reader/writer lock) remove their private .filelock- link directories with shutil.rmtree (a recursive delete) on a remembered path. They do not check that the path still names the directory they created. This happens on the hard-link route (a hard link is a second name for the same file). That route is every connection on macOS since 4.1.1 and any POSIX process without a usable /proc/self/fd (a Linux path that names the process's own open f…

GitHub Advisory Databaseで読む

2026/10/24 07:28、GitHub Advisory Databaseが「filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name」を公開しました (種別: 脆弱性アドバイザリ)。重大度は「警告」(medium) です。関連する技術: Python。CVE: CVE-2026-112937。