filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files

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

ReadWriteLock and AsyncReadWriteLock (the SQLite-backed reader/writer lock) hand SQLite a name they do not control. On Linux the lock validates its database through a descriptor (the number the kernel gives a process for an open file). It then connects SQLite to /proc/self/fd/ , a Linux path that names the process's own open file n. SQLite turns that path back into a plain path and reopens it by name, following symlinks (a symlink is a file that points at another path). On every POSIX route SQL…

Read on GitHub Advisory Database

On 10/24/2026, 06:59 AM, GitHub Advisory Database published "filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files" (type: Advisory). Severity is "High" (high). Related technologies: Python, SQLite. CVE: CVE-2026-112940.