CVE-2026-112914 — Tox-dev Filelock (tüm Sürümler) — CWE-363 · CWE-59
CVE-2026-112914 is a MEDIUM severity security vulnerability (CWE-363, CWE-59) (CVSS 5.3/10) affecting Tox-dev Filelock (tüm Sürümler). Technical vector analysis shows that an attacker can exploit this flaw via local access (AV:L) with low-privileged access (PR:L) with zero user interaction (UI:N), resulting in complete compromise of system confidentiality and integrity (C:H/I:H).
📄 Official NVD / MITRE Original Record Text
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.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-112914
CVSS 5.3/10 · MEDIUM · 20.10.2026
CWE: CWE-363, CWE-59
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Summary: 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.…
Affected: tox-dev:filelock
⚡ ATTACK CHAIN
Local/physical access | low-privilege account | no user interaction.
🌍 REAL WORLD IMPACT
All confidential data readable/stealable; data can be modified or deleted.
🛡️ REMEDIATION
→ Apply vendor security update for tox-dev:filelock.
→ Add WAF rule, create IDS alert for anomalous traffic.
⚠️ URGENCY
📋 Routine update cycle (30 days)
────────────────────────────────────────
[Kural Tabanlı Otomatik Güvenlik Analizi]
FOFA Query