Advisory

GHSA-9j6q-wvj5-jgjg

Details, part 3 of 3. The advisory

Details

Workarounds

  • Keep soft-lock directories writable only by the lock's own account, or use a sticky world-writable directory on Linux with fs.protected_symlinks=1 (the default), where the kernel refuses to follow another user's symlink and the check leaks nothing.
  • Do not take soft locks as root in directories other users can write.
  • Where a group-shared directory is unavoidable, give the marker an owner-write bit (the default mode does) and do not rely on ACL-granted access, so the os.access branch is not reached for the lock user's own marker. The other user's planted 0466 file still reaches it, so this only narrows the window.

Patched version

4.2.1.

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

Credits

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

  • 2026-10-15 23:08 UTC: report received (36 findings; this one rated medium by the scanner)
  • 2026-10-16 05:38 UTC: draft advisory created (first as part of GHSA-69hj-f68j-2879, then split out)
  • 2026-10-16 01:16 UTC: fix PR #835 opened

Sources & licences