filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders (tox-dev filelock)
At a glance
- Source
- NVD
- EPSS
- EPSS 0.13 % · percentile 3 ()
- State
- PUBLISHED
- Published
- Updated
- Assigner
- GitHub_M
- NVD status
- Analyzed
Description
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.
Weaknesses (CWE)
- CWE-367 — Time-of-check Time-of-use (TOCTOU) Race Condition
References
Scores
| Version | Score | Vector | Scored by |
|---|---|---|---|
| CVSS 3.1 | MEDIUM 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | GitHub_M |
| CVSS 3.1 | MEDIUM 4.7 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N | NVD · security-advisories@github.com (Secondary) |
Advisories
- GHSA-fq56-3cx3-fjxp — filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
European references
- ENISA EUVD · EUVD-2026-105025
- GCVE · GCVE-0-2026-112935
Affected configurations (NVD CPE)
cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*≥ 3.22.0 < 4.2.1
Affected products
| Product | Versions |
|---|---|
| tox-dev · filelock | affected >= 3.22.0, < 4.2.1 |
Sources
| Source | Licence |
|---|---|
| CVE List (CVEProject cvelistV5) | CVE Program Terms of Use |
| EPSS (FIRST.org) | FIRST — attribution requested |
| ENISA EUVD | ENISA — reproduction authorised, source acknowledged |
| NVD (NIST) via fkie-cad/nvd-json-data-feeds | Public domain — this product uses data from the NVD API but is not endorsed or certified by the NVD |