Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the <path>.rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the first acquisition to redirect lock-record writes into directories writable by the lock user. This issue is fixed in version 4.2.1.
CVSS Score
LOW
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/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-wfhq-q4j2-c37mExploitMitigationPatch
- https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37mExploitMitigationPatch
FAQ
What is CVE-2026-112941?
CVE-2026-112941 is a vulnerability with a CVSS score of 3.3 (LOW). filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the <path>.rw lock tree and resolve its names ...
How severe is CVE-2026-112941?
CVE-2026-112941 has been rated LOW with a CVSS base score of 3.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-112941?
Check the references section above for vendor advisories and patch information. Affected products include: Tox-Dev Filelock.