## filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

- 種別: advisory
- 重大度: medium
- 関連技術: python
- CVE: CVE-2026-112911
- 公開日時: 2026-10-28T21:08:59.000Z
- 情報源: GitHub Advisory Database (https://github.com/advisories/GHSA-9c4x-gm8v-wgc4)
- パーマリンク: https://vulnpulse.app/items/ghsa-ghsa-9c4x-gm8v-wgc4

影響: pip:filelock >= 3.30.0, <= 4.2.0 → 4.2.1
StrictSoftFileLock, AsyncStrictSoftFileLock, SoftReadWriteLock and AsyncSoftReadWriteLock keep their whole ownership state as files in a directory derived from the lock path ( .filelock/claims, .rw/{gen,holders}). When that directory already exists they adopt it after checking only that it is a real directory, not who owns it. Another local user who can create names in the lock's directory can create the tree before the first acquire on that path by the user running the lock (below: the lock us…