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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-112914— filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory

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 文件锁库。在版本 4.1.0 至 4.2.1 期间,SoftFileLock 在将过期的标记文件移开后,会根据文件名将其恢复,这使得同一本地用户若拥有重命名权限且处于非粘滞(non-sticky)锁目录中,便可替换为一个符号链接;若运行时遵循该符号链接且目标位于同一文件系统中,则可能导致锁持有者将其某个文件硬链接到锁目录中。该问题已在版本 4.2.1 中修复。

CVSS 5.3 · Medium

Possible ATT&CK Techniques 1 AI

T1565.002 · Transmitted Data Manipulation
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-112914

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: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory
Source: CVE Program / CVE List V5
Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. 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:L/I:H/A:N
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 >= 4.1.0, < 4.2.1 -

II. Public POCs for CVE-2026-112914

# 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-112914

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

Other References for CVE-2026-112914 (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-112911 6.3 MEDIUM filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user
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-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

V. Comments for CVE-2026-112914

No comments yet


Leave a comment