CVE-2026-112941
filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock
CVSS Score
3.3
EPSS Score
0.0%
EPSS Percentile
0th
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.
| CWE | CWE-367 |
| Vendor | tox-dev |
| Product | filelock |
| Published | Oct 20, 2026 |
Stay Ahead of the Next One
Get instant alerts for tox-dev filelock
Be the first to know when new low vulnerabilities affecting tox-dev filelock are published — delivered to Slack, Telegram or Discord.
Get Free Alerts →
Free · No credit card · 60 sec setup
CVSS v3 Breakdown
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None
Affected Versions
tox-dev / filelock
>= 4.1.0, < 4.2.1
References
github.com: https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m github.com: https://github.com/tox-dev/filelock/pull/842 github.com: https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03 github.com: https://github.com/tox-dev/filelock/releases/tag/4.2.1