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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-112940— filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files

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.20.4 至 4.2.1 版本中，ReadWriteLock 允许 SQLite 通过文件名重新打开数据库及其附属文件；在 POSIX 系统上，若攻击者对非粘滞（non-sticky）父目录拥有重命名权限，则可交换这些文件名，从而触发覆盖或删除操作；此外，若存在可写的相邻热日志（hot journal），攻击者还可利用其写入自定义内容以实现覆盖。该问题已在 4.2.1 版本中修复。

CVSS 7.1 · High
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-112940

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 ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files
Source: CVE Program / CVE List V5
Vulnerability Description
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. 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: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.20.4, < 4.2.1 -

II. Public POCs for CVE-2026-112940

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

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

Other References for CVE-2026-112940 (4)

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

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-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-363

V. Comments for CVE-2026-112940

No comments yet

Leave a comment