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。