filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name (tox-dev filelock)
At a glance
- Source
- NVD
- EPSS
- EPSS 0.16 % · percentile 5 ()
- State
- PUBLISHED
- Published
- Updated
- Assigner
- GitHub_M
- NVD status
- Analyzed
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.
Weaknesses (CWE)
- CWE-367 — Time-of-check Time-of-use (TOCTOU) Race Condition
References
Scores
| Version | Score | Vector | Scored by |
|---|---|---|---|
| CVSS 3.1 | MEDIUM 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | GitHub_M |
| CVSS 3.1 | MEDIUM 6.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L | NVD · security-advisories@github.com (Secondary) |
Advisories
- GHSA-jqc4-5cvw-7w85 — filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name
European references
- ENISA EUVD · EUVD-2026-105028
- GCVE · GCVE-0-2026-112937
Affected configurations (NVD CPE)
cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*≥ 4.1.0 < 4.2.1
Affected products
| Product | Versions |
|---|---|
| tox-dev · filelock | affected >= 4.1.0, < 4.2.1 |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |