## 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

- 種別: advisory
- 重大度: high
- 関連技術: python, sqlite
- CVE: CVE-2026-112940
- 公開日時: 2026-10-23T21:59:08.000Z
- 情報源: GitHub Advisory Database (https://github.com/advisories/GHSA-v4x8-3wr5-3wq8)
- パーマリンク: https://vulnpulse.app/items/ghsa-ghsa-v4x8-3wr5-3wq8

影響: 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…