Security Resilience

CVE-2026-112906

Race Condition in Tox-Dev Filelock 4.1.0 – 4.2.1

Public PoCRace Condition
Published
20 October 2026
Modified
27 October 2026
Patch / advisory
CVSS Score v3.1 4.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS Score 0.0017 6th percentile
Risk Priority 36 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-112906 is a medium-severity Use of Multiple Resources with Duplicate Identifier (CWE-694) vulnerability in Tox-Dev Filelock. Its CVSS base score is 4.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Evil Twin (T1557.004); ranked at the 6th 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 IA-4 (Identifier Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching…

more

modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

MITRE ATT&CK v20.0

T1557.004 Evil Twin Credential Access
Adversaries may host seemingly genuine Wi-Fi access points to deceive users into connecting to malicious networks as a way of supporting follow-on behaviors such as [Network Sniffing](https://attack.
T1553 Subvert Trust Controls Defense Impairment
Adversaries may undermine security controls that will either warn users of untrusted activity or prevent execution of untrusted programs.
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-112935Same product: Tox-Dev Filelock
CVE-2026-112941Same product: Tox-Dev Filelock
CVE-2026-112937Same product: Tox-Dev Filelock
CVE-2026-112914Same product: Tox-Dev Filelock
CVE-2026-112912Same product: Tox-Dev Filelock
CVE-2026-112940Same product: Tox-Dev Filelock
CVE-2026-112911Same product: Tox-Dev Filelock
CVE-2026-112909Same product: Tox-Dev Filelock

Affected Assets

tox-dev
filelock
4.1.0 — 4.2.1

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V8.4.1
  • V3.5.4
  • V6.8.1
  • V9.2.4

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Identifier management directly requires authorization and uniqueness controls that stop duplicate resource identifiers from being assigned or used.

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.

ID.AM-02 mostly match
blocks

Maintaining software/service inventories requires and enforces unique identifiers to avoid collisions.

PR.AA-01 mostly match
blocks

Managing identities and credentials for users/services/hardware directly requires unique identifiers.

ID.AM-08 partial match
blocks

Lifecycle management of assets includes identifier uniqueness as a supporting practice.

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 detect duplicate identifiers before deployment.

prevents

Secure coding standards can mandate unique identifier generation and validation.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-362, a class-level weakness, and none of its children carries one either.

References