CVE-2026-112940: CWE-363: Race Condition Enabling Link Following in tox-dev filelock
Description
A race condition vulnerability (CWE-363) exists in the tox-dev filelock Python package versions from 3.20.4 up to but not including 4.2.1. This flaw allows an attacker with rename access in a non-sticky parent directory on POSIX systems to swap file names used by SQLite, potentially causing overwrite or unlink operations. Exploitation requires a writable adjacent hot journal file to enable attacker-controlled content overwrites. The issue is resolved in version 4.2.1.
CVSS v3.1
Score 7.1high
Affected software
tox-dev
filelock
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The filelock package for Python, used for platform-independent file locking, contains a race condition vulnerability in its ReadWriteLock implementation affecting versions >=3.20.4 and <4.2.1. On POSIX systems, an attacker with rename privileges in a non-sticky parent directory can exploit this condition to swap SQLite database and side file names, leading to overwrite or unlink operations. Additionally, a writable adjacent hot journal file is required for the attacker to overwrite content of their choosing. This vulnerability is classified under CWE-363 (Race Condition) and has a CVSS 3.1 base score of 7.1, indicating high severity. The vulnerability was fixed in version 4.2.1 of filelock.
Potential Impact
An attacker with limited privileges (rename access in a non-sticky parent directory) can exploit this race condition to cause integrity violations by overwriting or unlinking SQLite database files or side files. This can lead to denial of service or data corruption. The vulnerability does not impact confidentiality but affects integrity and availability, as reflected in the CVSS vector (C:N/I:H/A:H). No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade the filelock package to version 4.2.1 or later, where this race condition vulnerability has been fixed. No other mitigations are indicated by the vendor advisory. Patch status is confirmed fixed in 4.2.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-10-19T21:30:47.245Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6ad782ec2cdf04f65638aa41
Added to database: 10/20/2026, 15:04:12 UTC
Last enriched: 10/20/2026, 15:18:16 UTC
Last updated: 10/20/2026, 19:06:08 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.