Analysis and contextual insights are available on OpenCVE Cloud.
No solution or workaround provided in the CVE record.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
Wed, 21 Oct 2026 21:30: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
|
Wed, 21 Oct 2026 00:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-59 | |
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Tue, 20 Oct 2026 16:45: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 14:45: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, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. This issue is fixed in version 4.2.1. | |
| Title | filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory | |
| Weaknesses | CWE-363 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-21T15:55:21.992Z
Reserved: 2026-10-19T20:16:09.858Z
Link: CVE-2026-112914
Updated: 2026-10-21T14:24:19.719Z
Status : Analyzed
Published: 2026-10-20T15:17:15.810
Modified: 2026-10-21T21:17:46.193
Link: CVE-2026-112914
OpenCVE Enrichment
Updated: 2026-10-20T17:00:18Z