Security Resilience

CVE-2026-112934

Tox-Dev Filelock 4.0.0 – 4.2.1

Public PoC
Published
20 October 2026
Modified
22 October 2026
Patch / advisory
CVSS Score v3.1 6.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
EPSS Score 0.0023 14th percentile
Risk Priority 45 floored blend · peak EPSS

CVSS 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-112934 is a medium-severity UNIX Hard Link (CWE-62) vulnerability in Tox-Dev Filelock. Its CVSS base score is 6.1 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 14th 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 AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1003.008 /etc/passwd and /etc/shadow Credential Access
Adversaries may attempt to dump the contents of <code>/etc/passwd</code> and <code>/etc/shadow</code> to enable offline password cracking.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1548 Abuse Elevation Control Mechanism Privilege Escalation
Adversaries may circumvent mechanisms designed to control privilege elevation to gain higher-level permissions.
T1548.001 Setuid and Setgid Privilege Escalation
An adversary may abuse configurations where an application has the setuid or setgid bits set in order to get code running in a different (and possibly more privileged) user’s context.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-22701Same product: Tox-Dev Filelock
CVE-2025-68146Same product: Tox-Dev Filelock
CVE-2026-112940Same product: Tox-Dev Filelock
CVE-2026-112914Same product: Tox-Dev Filelock
CVE-2026-112912Same product: Tox-Dev Filelock
CVE-2026-112935Same product: Tox-Dev Filelock
CVE-2026-112941Same product: Tox-Dev Filelock
CVE-2026-112937Same product: Tox-Dev Filelock
CVE-2026-112911Same product: Tox-Dev Filelock
CVE-2026-112906Same product: Tox-Dev Filelock

Affected Assets

tox-dev
filelock
4.0.0 — 4.2.1

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Access enforcement directly stops operations on files reached via unauthorized hard links by checking the actual target resource against authorizations.

Information flow enforcement can block unintended data access that occurs when a hard link crosses control-sphere boundaries.

Least privilege reduces the set of files an attacker can affect even if a hard-link name is resolved outside the intended sphere.

Preventing unintended transfer via shared resources (inodes) structurally blocks the effect of hard links that alias files across spheres.

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.

PR.AA-05 mostly match
blocks

Enforcing least-privilege permissions and authorization checks directly prevents operations on files reached via unauthorized hard links.

PR.PS-06 mostly match
blocks

Secure-development practices include safe file-open and link-handling routines that eliminate the described weakness.

PR.IR-01 partial match
blocks

Logical-access protections reduce the attack surface for hard-link traversal but do not address the coding flaw itself.

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.

finds

Security testing can discover hard-link issues but does not itself prevent them in production.

prevents

Training can raise developer awareness of hard-link attack patterns and the need to check for them, but CWE-62 is a subtle implementation defect requiring specific UNIX filesystem knowledge that most developers lack, so education prevents only a minority of instances.

prevents

Secure-coding practices can mandate safe file-open APIs and link validation, directly addressing the weakness.

finds

A.8.8's reach is disclosure-based (vendor advisories, vulnerability scanning) plus penetration testing; CWE-62 is an implementation defect that surfaces in CVEs (multiple examples listed) and can be found by competent penetration testers probing for hard-link attacks, but most instances in first-party code are not visible to disclosure-based scanning and require source-level review outside A.8.8's reach.

blocks

Configuration management can block some hard-link exploitation through hardening such as least privilege, disabling unnecessary services, restricting access to powerful utilities, and setting host parameters like kernel hard-link protection, but it does not stop a required vulnerable program from following hard links in code.

References