Python filelock: From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate
Affects python-filelockSource GCVE Database
Not known to be exploited · CVSS 5.8 Medium · 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 | 5.8 |
|---|
- Patch
- Available – fixed in 4.2.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:HExploitation 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.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1.
References
- ubuntu.com/security/CVE-2026-112938 (opens in a new tab)
- cve.org/CVERecord?id=CVE-2026-112938 (opens in a new tab)
- github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg (opens in a new tab)
- github.com/tox-dev/filelock/pull/839 (opens in a new tab)
- github.com/tox-dev/filelock/commit/aaa18595d29795fab599a69d6b184d9a505dab4b (opens in a new tab)
- github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03 (opens in a new tab)
- github.com/tox-dev/filelock/releases/tag/4.2.1 (opens in a new tab)