Advisory

GHSA-6627-m3xw-93mp

Details, part 3 of 3. The advisory

Details

Workarounds

Run processes that take strict locks with umask 022 or 077. Do not put a default ACL that grants other accounts write on the lock's parent directory; where you intend group sharing, trust every member of that group with the lock. Keep strict locks in a directory other users cannot write. For paths already in use, chmod 700 (or remove, while no process holds the lock) every existing <path>.filelock tree. Its mode comes from creation time and nothing changes it afterwards: find <dir> -maxdepth 1 -type d -name '*.filelock' -exec chmod -R go-w {} +.

Patched version

4.2.1.

Fix: https://github.com/tox-dev/filelock/pull/839

Credits

Reported by Anthropic's OSS Scanner (automated analysis), 15 October 2026; reviewed by the maintainers.

  • 2026-10-15 23:08 UTC: report received (finding ANT-2026-AD6SUOON, scanned commit b831496b0273)
  • 2026-10-16 01:31 UTC: fix PR #839 opened
  • 2026-10-16 05:39 UTC: draft advisory created (first as part of GHSA-9c4x-gm8v-wgc4, then split into this advisory)

Sources & licences