tox-dev filelock up to 4.2.0 WindowsFileLock src/filelock/_windows.py _open_non_reparse_fd mode permission assignment
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 1.85 |
Summary
A vulnerability classified as problematic has been found in tox-dev filelock up to 4.2.0. This issue affects the function _open_non_reparse_fd of the file src/filelock/_windows.py of the component WindowsFileLock. This manipulation of the argument mode causes permission assignment.
This vulnerability is registered as CVE-2026-112910. The attack needs to be launched locally. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability was found in tox-dev filelock up to 4.2.0. It has been declared as problematic. Affected by this vulnerability is the function _open_non_reparse_fd of the file src/filelock/_windows.py of the component WindowsFileLock. The manipulation of the argument mode with an unknown input leads to a permission assignment vulnerability. The CWE definition for the vulnerability is CWE-732. The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors. As an impact it is known to affect confidentiality, integrity, and availability.
This vulnerability is known as CVE-2026-112910. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available.
Upgrading to version 4.2.1 eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Permission assignmentCWE: CWE-732 / CWE-275 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: filelock 4.2.1
Timeline
10/28/2026 Advisory disclosed10/28/2026 VulDB entry created
10/28/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-112910 (🔒)
GCVE (CVE): GCVE-0-2026-112910
GCVE (VulDB): GCVE-100-428245
Entry
Created: 10/28/2026 23:08Changes: 10/28/2026 23:08 (53)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.