← CVE Radar
CVE-2026-112908filelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live hold
filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1.
5.3 MEDIUMEPSS 0.12%Not in KEVNVD: Awaiting Analysis
Overview
Severity
| Score | Severity | Version | Vector String |
|---|---|---|---|
| 5.3 | MEDIUM | 3.1GitHub_M (CNA) | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L |
Details
- CVE ID
- CVE-2026-112908
- Status
- Awaiting Analysis
- Assigner (CNA)
- GitHub_M
- Published
- Nov 5, 2026
- Last modified
- 2026-11-06 21:40 UTC
- Weaknesses
- CWE-732 · Incorrect Permission Assignment for Critical Resource
Affected Products
As published by the CNA in the CVE record.
tox-devfilelock1 version range
- >= 3.30.0, < 4.2.1
References
- github.com https://github.com/tox-dev/filelock/commit/8cf51802158b9cf7e1fc560c2da30491a662cfde
- github.com https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- github.com https://github.com/tox-dev/filelock/pull/839
- github.com https://github.com/tox-dev/filelock/releases/tag/4.2.1
- github.com https://github.com/tox-dev/filelock/security/advisories/GHSA-6627-m3xw-93mp