CVE-2026-112937 — Tox-dev Filelock (tüm Sürümler) — CWE-367
CVE-2026-112937 is a MEDIUM severity security vulnerability (CWE-367) (CVSS 6.1/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), posing a direct security risk to affected deployments.
📄 Official NVD / MITRE Original Record Text
filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
CVE-2026-112937
CVSS 6.1/10 · MEDIUM · 20.10.2026
CWE: CWE-367
Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
🎯 WHAT IS THIS VULNERABILITY?
Summary: filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.
Affected: tox-dev:filelock
⚡ ATTACK CHAIN
Local/physical access | low-privilege account | no user interaction | low complexity.
🌍 REAL WORLD IMPACT
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