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 (2026-10-21 08:23 UTC)

Does this affect you?

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

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for tox-dev filelock

Exploited in the last 30 days

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: Undergoing Analysis
Record last updated: Oct 20, 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

References

https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85x-refsource-confirm
https://github.com/tox-dev/filelock/pull/834x-refsource-misc
https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2dx-refsource-misc
https://github.com/tox-dev/filelock/releases/tag/4.2.1x-refsource-misc

The CVE record on cve.org NVD's entry

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.