tox-dev filelock up to 4.2.0 SoftFileLock src/filelock/_soft.py _read_lock_file resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.2 | $0-$5k | 3.94 |
Summary
A vulnerability was found in tox-dev filelock up to 4.2.0. It has been rated as problematic. Affected by this vulnerability is the function _read_lock_file of the file src/filelock/_soft.py of the component SoftFileLock. This manipulation causes resource consumption.
The identification of this vulnerability is CVE-2026-112907. The attack can only be executed locally. There is no exploit available.
Upgrading the affected component is advised.
Details
A vulnerability classified as problematic was found in tox-dev filelock up to 4.2.0. Affected by this vulnerability is the function _read_lock_file of the file src/filelock/_soft.py of the component SoftFileLock. The manipulation with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability.
This vulnerability is known as CVE-2026-112907. 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: 3.3VulDB Meta Temp Score: 3.2
VulDB Base Score: 3.3
VulDB Temp Score: 3.2
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: Resource consumptionCWE: CWE-400 / CWE-404
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/26/2026 Advisory disclosed10/26/2026 VulDB entry created
10/26/2026 VulDB entry last update
Sources
Status: ConfirmedCVE: CVE-2026-112907 (🔒)
GCVE (CVE): GCVE-0-2026-112907
GCVE (VulDB): GCVE-100-426349
Entry
Created: 10/26/2026 10:25Changes: 10/26/2026 10:25 (52)
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.