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 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 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. This issue is fixed in version 4.2.1. | |
| Title | filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion | |
| Weaknesses | CWE-283 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T14:21:24.480Z
Reserved: 2026-10-19T20:16:09.858Z
Link: CVE-2026-112911
No data.
Status : Awaiting Analysis
Published: 2026-10-20T15:17:15.473
Modified: 2026-10-20T19:50:26.943
Link: CVE-2026-112911
No data.
OpenCVE Enrichment
Updated: 2026-10-20T17:00:18Z
-
CWE-283
Unverified Ownership