Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-112911— filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

Quick assessment

Affected
tox-dev filelock
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

filelock 是一个与平台无关的 Python 文件锁工具。在 3.30.0 到 4.2.1 版本期间，StrictSoftFileLock（3.30.0 及更高版本）和 SoftReadWriteLock（4.0.0 及更高版本）可能会采用由同一父目录下的其他本地用户预先创建的协议目录。这使得该用户能够篡改协议状态并允许并发持有者，从而引发安全风险。该问题已在 4.2.1 版本中修复。

CVSS 6.3 · Medium

Possible ATT&CK Techniques 1 AI

T1552 · Unsecured Credentials
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-112911

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion
Source: CVE Program / CVE List V5
Vulnerability Description
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. This issue is fixed in version 4.2.1.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
未经验证的属主
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
tox-dev filelock >= 3.30.0, < 4.2.1 -

II. Public POCs for CVE-2026-112911

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-112911

请登录查看更多情报信息。

Other References for CVE-2026-112911 (4)

Same Patch Batch · tox-dev · 2026-10-20 · 13 CVEs total

CVE-2026-112940 7.1 HIGH filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or
CVE-2026-112909 6.1 MEDIUM filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-
CVE-2026-112934 6.1 MEDIUM filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named
CVE-2026-112936 6.1 MEDIUM filelock: ReadWriteLock follows a symlink at the lock path into SQLite
CVE-2026-112937 6.1 MEDIUM filelock: ReadWriteLock on the hard-link route deletes any directory another user renames
CVE-2026-112915 5.5 MEDIUM filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardle
CVE-2026-112914 5.3 MEDIUM filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-lin
CVE-2026-112906 4.7 MEDIUM filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre
CVE-2026-112935 4.7 MEDIUM filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number
CVE-2026-112939 4.7 MEDIUM filelock: SoftFileLock removes a live holder's marker when another user forges the PID in
CVE-2026-112941 3.3 LOW filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and wri
CVE-2026-112912 2.5 LOW filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists

IV. Related Vulnerabilities

Same product: filelock
Same vendor: tox-dev
Same weakness: CWE-283

V. Comments for CVE-2026-112911

No comments yet

Leave a comment