Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Tox-Dev | Filelock | >= 4.0.0, < 4.2.1 |
Related Weaknesses (CWE)
References
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77Patch
- https://github.com/tox-dev/filelock/pull/842Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845ExploitMitigationVendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845ExploitMitigationVendor Advisory
FAQ
What is CVE-2026-112934?
CVE-2026-112934 is a vulnerability with a CVSS score of 6.1 (MEDIUM). filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock director...
How severe is CVE-2026-112934?
CVE-2026-112934 has been rated MEDIUM with a CVSS base score of 6.1/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112934?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.