Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 20 Oct 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Tox-dev
Tox-dev filelock |
|
| Vendors & Products |
Tox-dev
Tox-dev filelock |
Tue, 20 Oct 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name | |
| Weaknesses | CWE-367 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T14:36:28.129Z
Reserved: 2026-10-19T21:30:47.244Z
Link: CVE-2026-112937
No data.
Status : Awaiting Analysis
Published: 2026-10-20T15:17:16.527
Modified: 2026-10-20T19:50:26.943
Link: CVE-2026-112937
No data.
OpenCVE Enrichment
Updated: 2026-10-20T18:15:14Z
-
CWE-367
Time-of-check Time-of-use (TOCTOU) Race Condition