CVE-2026-112939: CWE-345: Insufficient Verification of Data Authenticity in tox-dev filelock
Description
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can trust a forged process identifier in a marker that an attacker can modify but cannot remove, allowing an authorized contender such as another process of the holder's account or root to act as a confused deputy, remove the live marker, and admit another holder. This issue is fixed in version 4.2.1.
CVSS v3.1
Score 4.7medium
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
CVE-2026-112939 describes a weakness in tox-dev's filelock library, specifically in the SoftFileLock implementation between versions 3.22.0 and 4.2.0 inclusive. The flaw is due to insufficient verification of the authenticity of a process identifier stored in a marker file. An attacker with authorized access (e.g., another process running under the same user or root) can forge this identifier, remove the live marker, and thereby allow another process to acquire the lock improperly. This can lead to unauthorized lock acquisition and potential interference with file locking mechanisms. The issue is resolved in version 4.2.1.
Potential Impact
The vulnerability allows an authorized contender process to bypass proper lock ownership verification by forging a process identifier in the lock marker. This can lead to unauthorized lock acquisition, potentially causing interference or race conditions in applications relying on filelock for synchronization. The impact is limited to integrity (I:H) with no confidentiality or availability impact reported. Exploitation requires local access with at least limited privileges and high attack complexity.
Mitigation Recommendations
Upgrade to filelock version 4.2.1 or later, where this vulnerability is fixed. No other mitigations are specified or recommended by the vendor. Since this is a local privilege issue requiring authorized access, restricting local user permissions may reduce risk but does not fully mitigate the vulnerability.
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: 6ad782ec2cdf04f65638aa40
Added to database: 10/20/2026, 15:04:12 UTC
Last enriched: 10/20/2026, 15:18:50 UTC
Last updated: 10/20/2026, 19:06:08 UTC
Views: 7
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.