Vulnerability 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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | >= 3.22.0, < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4dPatch
- https://github.com/tox-dev/filelock/pull/843Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fq56-3cx3-fjxpExploitMitigationPatch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fq56-3cx3-fjxpExploitMitigationPatch
FAQ
What is CVE-2026-112935?
CVE-2026-112935 is a vulnerability with a CVSS score of 4.7 (MEDIUM). 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 conte...
How severe is CVE-2026-112935?
CVE-2026-112935 has been rated MEDIUM with a CVSS base score of 4.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112935?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.