CVE-2026-112935
filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders
- Medium 4.7
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.
Key facts
- Published
- 20 Oct 2026
- Last changed
- 28 Oct 2026
- Assigned by
- GitHub_M
- EPSS
- 0.132% likely to be exploited in the next 30 days, higher than 2.842% of CVEs (scores for 18 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 4.7CVSS 3.1, Mediumfrom the CNA (GitHub_M)
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| tox-dev | filelock |
|
Timeline
- 20 Oct 2026 Published