Back to CVE records
Medium 6.1Published Oct 20, 2026

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

Updated under an hour ago ()

Does this affect you?

It affects tox-dev filelock and 1 other product. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

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.

CVSS
6.1 MEDIUM (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
Weakness (CWE)
CWE-367
Known exploited
Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days)
Not loaded for this CVE
Assigned by
GitHub_M
NVD analysis
Analyzed
Record last updated
Oct 21, 2026
First seen by InfoSec Signals
Oct 20, 2026

Affected products

Affected products
tox-dev filelock
tox_dev:filelock (from the name)
from 4.1.0, < 4.2.1
CNA record
tox-dev filelock
tox-dev:filelock
from 4.1.0 before 4.2.1
NVD

References

References

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.

Your cookie choices
We use essential cookies to run this site, and, only with your consent, an advertising cookie from Google to measure whether our ads lead to sign-ups and subscriptions. See our for details.