CVE-2026-112938filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user chooses
- 5.8MediumCVSS base score
- 0.11%Exploitation in 30 daysEPSS · top 99% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
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.
Timeline
ID reserved
By GitHub_M
- 17 days later
· 17 days later
Published
- 4 days later
· 4 days later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.1 | Medium5.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H |
| NVDNVD · Awaiting Analysis | 3.1 | Medium5.8 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H |
- EPSS (exploitation in 30 days)
- 0.11% · top 99% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.8.
Affected products
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- PyPIfilelockGHSA-m462-7rxw-wvpg (opens in a new tab)
References
References5
- https://github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg (opens in a new tab)x_refsource_CONFIRM
- https://github.com/tox-dev/filelock/pull/839 (opens in a new tab)x_refsource_MISC
- https://github.com/tox-dev/filelock/commit/aaa18595d29795fab599a69d6b184d9a505dab4b (opens in a new tab)x_refsource_MISC
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03 (opens in a new tab)x_refsource_MISC
- https://github.com/tox-dev/filelock/releases/tag/4.2.1 (opens in a new tab)x_refsource_MISC
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-117814 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-m462-7rxw-wvpg (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-112938)Record last updated .