CVE-2026-112938
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.
Weakness
- CWE-363: Race Condition Enabling Link Following
CISA SSVC decision points
| Exploitation | none |
|---|---|
| Automatable | no |
| Technical impact | partial |
| Scored | 2026-11-09 |
Timeline
- 2026-10-28GitHub advisory published (GHSA-m462-7rxw-wvpg)8 days before publication
- 2026-11-05Published by the CNA21:51 UTC
- 2026-11-09CISA SSVC decision recorded4 days after publication
Exploit and advisory records
GitHub advisory GHSA-m462-7rxw-wvpg, affected packages:
| Package | Vulnerable versions | Fixed in |
|---|---|---|
| PyPI filelock | from 3.30.0 before 4.2.1 | 4.2.1 |
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| tox-dev filelock |
References
- https://github.com/tox-dev/filelock/commit/aaa18595d29795fab599a69d6b184d9a505dab4b
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- https://github.com/tox-dev/filelock/pull/839
- https://github.com/tox-dev/filelock/releases/tag/4.2.1
- https://github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-112938'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-112938'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-112938'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-112938'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).