CVE-2026-112938
MEDIUMDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 1% of all known CVEs.
References
Related Vulnerabilities
Other CWE-363 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2022-21658 | High | 7.3 | 1.5% | - | Fix |
| CVE-2025-31133 | High | 7.8 | 1.2% | - | Fix |
| CVE-2025-52565 | High | 7.5 | 0.8% | - | Fix |
| CVE-2025-52881 | High | 7.5 | 0.8% | - | Fix |
| CVE-2024-27102 | Critical | 9.9 | 0.5% | - | Fix |
| CVE-2024-45310 | Low | 3.6 | 0.3% | - | Fix |
Common questions
How do I fix CVE-2026-112938?
Upgrade python-filelock on debian unstable to 4.2.2-1 or later.
Is CVE-2026-112938 being actively exploited?
Not that we know of. CVE-2026-112938 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 1% of all scored CVEs.
How severe is CVE-2026-112938?
CVE-2026-112938 has a CVSS v3 base score of 5.8, rated medium. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-112938 affect?
Published advisories record a fix for python-filelock (Debian). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-112938
Markdown
[](https://tridentstack.com/cve/CVE-2026-112938)HTML
<a href="https://tridentstack.com/cve/CVE-2026-112938"><img src="https://tridentstack.com/cve/badge/CVE-2026-112938.svg" alt="CVE-2026-112938"></a>Check your Linux endpoints for this class of vulnerability
TridentStack Control continuously scans Linux endpoints for known vulnerabilities and deploys the fixes from the same console. 200 endpoints free forever, no credit card.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-09.