CVE-2026-112911
Tox-Dev Filelock 3.30.0 – 4.2.1
Raw vector
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:HCVSS 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-112911 is a medium-severity Unverified Ownership (CWE-283) vulnerability in Tox-Dev Filelock. Its CVSS base score is 6.3 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Credential Access (T1212); ranked at the 4th 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-16 (Security and Privacy Attributes) and AC-24 (Access Control Decisions) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105018
Vulnerability Data
filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user…
more
to alter protocol state and admit concurrent holders. 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
—
—
- 3 hardening rules · 3 OS baselines
—
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Associating ownership as a security attribute enables subsequent verification of resource ownership.
Requiring access decisions to consider all relevant attributes includes ownership verification.
A reference monitor provides the tamperproof mechanism that can enforce ownership checks.
Access enforcement directly requires verifying ownership before granting access to resources.
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.
Enforcing defined access permissions and authorizations directly prevents missing ownership verification for resources.
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.
Access control policies can require ownership verification before granting access to critical resources.
A.8.28 mandates secure coding practices — threat modelling, secure coding standards, peer review, and analysis of common programming errors — that would catch some instances of missing ownership verification, but the control is a process mandate whose effectiveness depends on implementation rigor, leaving a nameable remainder of instances where the practice is not applied or fails.
A.8.29's SOURCE+RUNTIME reach finds most CWE-283 instances: code review catches the missing ownership check (it is literal in source, unlike CWE-798's build-time credentials), and penetration testing surfaces exploitable cases like the demonstrative process-kill example. The remainder is ownership checks missing in code paths not exercised by tests or not selected for review, and static analysis has limited rules for this semantic 'should this code check ownership?' question.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary code-level ownership-verification defects in delivered software the way those practices do, at `partial` -- the same reasoning the owner applied to A.8.30 -> CWE-134.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over our cross-walk; rows rated `none` are excluded, and each rule says how its mapping was checked.
Definition changed on 29 October 2026. Until then this section listed every rule rated above none, partial included. From that date it lists rules whose mapping is rated full or mostly and checked at llm_unverified or higher; partial mappings show when you ask.
No rule maps to these weaknesses at full or mostly. Tick the option above to see the partial mappings.
Windows Server 2016 (1 partial rule)
- V-224831 Local volumes must use a format that supports NTFS attributes. blocks CWE-283
Windows Server 2019 (1 partial rule)
- V-205663 Windows Server 2019 local volumes must use a format that supports NTFS attributes. blocks CWE-283