Python filelock: From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file
Affects python-filelockSource GCVE Database
Not known to be exploited · CVSS 2.5 Low · fixed in 4.2.1 : update python-filelock when convenient.
Data as of 18 Nov 2026, 15:20 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 2.5 |
|---|
- Patch
- Available – fixed in 4.2.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:LExploitation evidence
Disclosed: evidence found.
CVE published 5 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10python-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu Pro 24.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/nobleOther threats | Affected
| Fixed in– |
Ubuntu Pro 22.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/jammyOther threats | Affected
| Fixed in– |
Ubuntu Pro 20.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/focalOther threats | Affected
| Fixed in– |
Ubuntu Pro 18.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. This issue is fixed in version 4.2.1.
References
- ubuntu.com/security/CVE-2026-112907 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-112907 (opens in a new tab)
- github.com/tox-dev/filelock/security/advisories/GHSA-567q-5qvw-pf92 (opens in a new tab)
- github.com/tox-dev/filelock/pull/835 (opens in a new tab)
- github.com/tox-dev/filelock/commit/97d694a9a3ee1721d6c79a480174dfd9b060a080 (opens in a new tab)
- github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a (opens in a new tab)
- github.com/tox-dev/filelock/releases/tag/4.2.1 (opens in a new tab)