Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-112914 is a medium-severity Race Condition Enabling Link Following (CWE-363) vulnerability in Tox-Dev Filelock. Its CVSS base score is 5.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 5th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105020
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V15.4.2
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
AC-3 enforces access decisions at the moment of use, limiting damage when a replaced link causes access to an unintended object.
SA-8 mandates security engineering principles that include atomic operations and safe file handling, preventing introduction of check-then-use race conditions.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent TOCTOU race conditions such as link-following by requiring atomic operations and safe file handling.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Security testing can detect link-following races, but testing alone does not prevent the weakness.
Training developers about secure file handling practices (checking for symlinks, using safe file APIs, avoiding predictable temp filenames) reduces some instances of link-following defects, but the effect is a minority one because the practice is fallible and the stronger control is A.8.29 security testing, consistent with the A.8.28 -> CWE-79 and A.6.3 -> CWE-598 anchors.
Secure coding standards directly address TOCTOU and link-following vulnerabilities, covering most of the weakness while the control also covers many other issues.
A.8.30 carries its effect through the secure-development practices (8.25–8.29) its contract requires of the supplier, so a TOCTOU/link-following defect in delivered code is reduced the way those practices reduce ordinary code defects; the clause sits at its declared ceiling of `partial` because the effect depends on the supplier's implementation of secure coding guidance.
A.8.8's reach is DISCLOSURE — it surfaces link-following flaws only where they appear as published advisories in third-party components in the inventory. CWE-59 does surface as CVEs (many observed examples), so the disclosed share is non-trivial, but most link-following instances live in first-party code or in third-party components without a published advisory, which A.8.8 does not reach.