CVE-2026-112938
Last modified
CVE-2026-112938 is a medium-severity vulnerability rated 5.8/10 on the CVSS scale. 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.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| tox-dev | filelock | >= 3.30.0, < 4.2.1 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-112938?
How severe is CVE-2026-112938?
How do I fix CVE-2026-112938?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-112922A flaw was found in Ghostscript. A remote attacker could exp…3.3
- CVE-2026-11293Use after free in Input in Google Chrome prior to 149.0.7827…9.6
- CVE-2026-112934filelock is a platform-independent file lock for Python. Fro…6.1
- CVE-2026-112935filelock is a platform-independent file lock for Python. Fro…4.7
- CVE-2026-112936filelock is a platform-independent file lock for Python. Fro…6.1
- CVE-2026-112937filelock is a platform-independent file lock for Python. Fro…6.1
- CVE-2026-112939filelock is a platform-independent file lock for Python. Fro…4.7
- CVE-2026-11294Inappropriate implementation in Passwords in Google Chrome p…4.3
- CVE-2026-112940filelock is a platform-independent file lock for Python. Fro…7.1
- CVE-2026-112941filelock is a platform-independent file lock for Python. Fro…3.3
- CVE-2026-112942launch-editor allows users to open files with line numbers i…7.5
- CVE-2026-112943launch-editor allows users to open files with line numbers i…6.3
Are you affected by CVE-2026-112938?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
