Quick answers
- Is CVE-2026-112906 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-112906 being exploited in the wild.
- How severe is CVE-2026-112906?
- Medium severity, with a CVSS score of 4.7, published 20 October 2026.
- Which products and versions are affected?
- filelock (PyPI) >= 4.1.0, <= 4.2.0, ECOSYSTEM:introduced=4.1.0,fixed=4.2.1; Tox-Dev Filelock 4.1.0 to 4.2.0.
- Is there a fix for CVE-2026-112906?
- Yes. filelock (PyPI): upgrade to 4.2.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-112906 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-112906?
- Check whether you run filelock (PyPI) or Tox-Dev Filelock at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- filelock (PyPI): upgrade to 4.2.1 or later
pip install "filelock>=4.2.1"
Technical details
SoftFileLock maintains lock state via marker files on the filesystem. The vulnerability is a race condition where an attacker can pre-date and remove their own marker, then exploit inode reuse when multiple processes are waiting and filesystem modification times align, causing the lock mechanism to incorrectly classify a fresh, live marker as stale and remove it. This breaks the lock's mutual exclusion guarantee, allowing concurrent access to protected resources. The issue is fixed in version 4.2.1 by using atomic marker exchange operations on platforms that support them.
Affected products
- tox-dev filelock 4.1.0 to 4.2.0
Identifiers
- CVE-2026-112906
- GHSA-2g95-wg33-c5x2
Timeline
- 2026-10-20: disclosed
- 2026-10-17: patched: fix commit date