Skip to main content

CVE-2026-112936: CWE-59: Improper Link Resolution Before File Access ('Link Following') in tox-dev filelock

0
Medium
VulnerabilityCVE-2026-112936cvecve-2026-112936cwe-59cwe-668
Published: 10/20/2026 (10/20/2026, 14:34:47 UTC)
Source: CVE Database V5
Vendor/Project: tox-dev
Product: filelock

Description

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory to redirect database creation and locking or split mutual exclusion between targets. This issue is fixed in version 4.0.9.

CVSS v3.1

Score 6.1medium

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
Low
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L

Affected software

tox-dev

filelock

Affected versions
>=3.20.4 <4.0.9
filelock
pkg:pypi/filelock
Affected versions
>=3.20.4 <4.0.9

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/20/2026, 15:18:58 UTC

Technical Analysis

The tox-dev filelock package versions >=3.20.4 and <4.0.9 contain a CWE-59 (Improper Link Resolution Before File Access) vulnerability in the ReadWriteLock and AsyncReadWriteLock components. These versions resolve the lock path and pass it to SQLite without rejecting a final symbolic link. This flaw enables a local attacker who can create entries in the lock directory to redirect database creation and locking operations or split mutual exclusion between targets. The issue is addressed in version 4.0.9.

Potential Impact

An attacker with local access and the ability to create names in the lock directory can exploit this vulnerability to redirect database creation and locking. This can lead to interference with the intended mutual exclusion, potentially causing denial of service or inconsistent locking behavior. The vulnerability does not impact confidentiality but can affect integrity and availability of the locking mechanism.

Mitigation Recommendations

Upgrade to tox-dev filelock version 4.0.9 or later, where this vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-10-19T21:30:47.244Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad782ea2cdf04f65638a99b

Added to database: 10/20/2026, 15:04:10 UTC

Last enriched: 10/20/2026, 15:18:58 UTC

Last updated: 10/20/2026, 19:06:08 UTC

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses