CVE-2026-112940
filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files
CVSS Score
7.1
EPSS Score
0.0%
EPSS Percentile
0th
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. This issue is fixed in version 4.2.1.
| CWE | CWE-363 |
| 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 high 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:H/A:H Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High
Affected Versions
tox-dev / filelock
>= 3.20.4, < 4.2.1
References
github.com: https://github.com/tox-dev/filelock/security/advisories/GHSA-v4x8-3wr5-3wq8 github.com: https://github.com/tox-dev/filelock/pull/834 github.com: https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d github.com: https://github.com/tox-dev/filelock/releases/tag/4.2.1