Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Wed, 21 Oct 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:* |
Wed, 21 Oct 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
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
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-21T15:55:14.113Z
Reserved: 2026-10-19T21:30:47.244Z
Link: CVE-2026-112937
Updated: 2026-10-21T14:24:21.152Z
Status : Analyzed
Published: 2026-10-20T15:17:16.527
Modified: 2026-10-21T18:05:42.917
Link: CVE-2026-112937
No data.
OpenCVE Enrichment
Updated: 2026-10-20T18:15:14Z