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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-112934— filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

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.0.0 至 4.2.1 期间，SoftReadWriteLock 通过名称刷新持有者记录，这使得拥有锁目录重命名权限的其他本地用户能够将记录替换为命名管道（named pipe），从而阻塞锁的获取；或者在允许硬链接的策略下，将记录链接到可访问的目标文件，导致锁的使用者通过该文件进行写入。此问题已在版本 4.2.1 中修复。

CVSS 6.1 · Medium

Possible ATT&CK Techniques 2 AI

T1055 · Process Injection T1562.004
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-112934

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: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record
Source: CVE Program / CVE List V5
Vulnerability Description
filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
UNIX硬链接
Source: CVE Program / CVE List V5

Affected Products

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

II. Public POCs for CVE-2026-112934

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

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

Other References for CVE-2026-112934 (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-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-62

V. Comments for CVE-2026-112934

No comments yet

Leave a comment