Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | >= 4.1.0, < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/740ff666b62a88496c8d7394e4e6230605e4dPatch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-2g95-wg33-c5x2ExploitMitigationPatch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-2g95-wg33-c5x2ExploitMitigationPatch
FAQ
What is CVE-2026-112906?
CVE-2026-112906 is a vulnerability with a CVSS score of 4.7 (MEDIUM). filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, a...
How severe is CVE-2026-112906?
CVE-2026-112906 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-112906?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.