Skip to main content

CVE-2026-112911: CWE-283: Unverified Ownership in tox-dev filelock

0
Medium
VulnerabilityCVE-2026-112911cvecve-2026-112911cwe-283
Published: 10/20/2026 (10/20/2026, 14:21:24 UTC)
Source: CVE Database V5
Vendor/Project: tox-dev
Product: filelock

Description

A vulnerability in the tox-dev filelock Python package versions from 3.30.0 up to but not including 4.2.1 allows a local user to adopt a protocol directory created by another user in a shared parent directory. This can lead to unauthorized alteration of protocol state and concurrent lock holders. The issue is fixed in version 4.2.1.

CVSS v3.1

Score 6.3medium

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

Affected software

tox-dev

filelock

Affected versions
>=3.30.0 <4.2.1
filelock
pkg:pypi/filelock
Affected versions
>=3.30.0 <4.2.1

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:03:44 UTC

Technical Analysis

The filelock package for Python, used for platform-independent file locking, contains an unverified ownership vulnerability (CWE-283) affecting StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 through 4.2.0. This flaw allows a local user to take over a protocol directory created by another user within a shared parent directory, enabling them to modify the protocol state and allow multiple concurrent holders of the lock. The vulnerability is resolved in version 4.2.1.

Potential Impact

An attacker with local access can manipulate the protocol directory ownership, causing concurrent holders of a lock that should be exclusive. This can lead to integrity and availability impacts, as indicated by the CVSS vector (no confidentiality impact, but high integrity and availability impact).

Mitigation Recommendations

Upgrade to filelock version 4.2.1 or later, where this vulnerability is fixed. No other mitigations are indicated.

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-19T20:16:09.858Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ad77f652cdf04f65637ac0f

Added to database: 10/20/2026, 14:49:09 UTC

Last enriched: 10/20/2026, 15:03:44 UTC

Last updated: 10/20/2026, 15:28:32 UTC

Views: 3

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