What’s Vulnerable › Vulnerabilities

CVE-2026-112937: filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

• Severity: medium (CVSS 6.1 v3.1)
• Exploited in the wild: not listed in CISA KEV
• EPSS: 0.2% probability of exploitation in the next 30 days
• Public exploit or detection template: yes
• Published: 2026-10-20 · updated 2026-10-21
• Weakness: CWE-367

Description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.

Affected products

• tox-dev filelock: from 4.1.0 before 4.2.1 — fixed in 4.2.1

How to fix

Upgrade to a fixed version: tox-dev filelock 4.2.1. Check the vendor advisory for mitigations.

References

• https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d
• https://github.com/tox-dev/filelock/pull/834
• https://github.com/tox-dev/filelock/releases/tag/4.2.1
• https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85

Get alerted when CVE-2026-112937 or the next vulnerability affects your stack