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.
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 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 20 Oct 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can trust a forged process identifier in a marker that an attacker can modify but cannot remove, allowing an authorized contender such as another process of the holder's account or root to act as a confused deputy, remove the live marker, and admit another holder. This issue is fixed in version 4.2.1. | |
| Title | filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker | |
| Weaknesses | CWE-345 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T15:14:56.836Z
Reserved: 2026-10-19T21:30:47.245Z
Link: CVE-2026-112939
Updated: 2026-10-20T15:14:48.883Z
Status : Received
Published: 2026-10-20T15:17:16.663
Modified: 2026-10-20T16:17:04.630
Link: CVE-2026-112939
No data.
OpenCVE Enrichment
Updated: 2026-10-20T17:30:13Z
-
CWE-345
Insufficient Verification of Data Authenticity