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 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:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. This issue is fixed in version 4.2.1. | |
| Title | filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path | |
| Weaknesses | CWE-706 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-10-20T14:16:02.317Z
Reserved: 2026-10-19T20:16:09.857Z
Link: CVE-2026-112909
No data.
Status : Received
Published: 2026-10-20T15:17:15.313
Modified: 2026-10-20T15:17:15.313
Link: CVE-2026-112909
No data.
OpenCVE Enrichment
Updated: 2026-10-20T17:00:18Z