CVE-2026-112913
filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock and AsyncReadWriteLock on Windows use _connect to attach SQLite to the lock database by pathname, allowing another local account that can create adjacent names to place a database-wal or database-journal side file before acquisition. An undeletable WAL file makes each read or write acquisition fail immediately with sqlite3.OperationalError regardless of timeout. Separately, when the database contains at least one table, a hot journal that grants the lock account modify rights can cause SQLite recovery to delete a file named by that journal only when the lock account has permission to delete the target. The issue requires a directory writable by another account, such as a shared Windows temporary directory, and does not affect private directories. This issue is fixed in version 4.2.1.
Fixes and workarounds
Fix
filelock (PyPI): OSV reports a fixed version 4.2.1. Check the advisory for supported release branches.
Source: OSV GHSA-9vhv-jxww-xfm5Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| filelock tox-dev |
>= 3.20.4, < 4.2.1 (affected) | CNA: GitHub_M |
filelockfilelock
PyPI |
3.20.4 (affected, PyPI) 3.21.0 (affected, PyPI) 3.21.1 (affected, PyPI) 3.21.2 (affected, PyPI) 3.22.0 (affected, PyPI) 3.23.0 (affected, PyPI) 3.24.0 (affected, PyPI) 3.24.1 (affected, PyPI) 3.24.2 (affected, PyPI) 3.24.3 (affected, PyPI) 3.25.0 (affected, PyPI) 3.25.1 (affected, PyPI) 3.25.2 (affected, PyPI) 3.28.0 (affected, PyPI) 3.29.0 (affected, PyPI) 3.29.1 (affected, PyPI) 3.29.2 (affected, PyPI) 3.29.3 (affected, PyPI) 3.29.4 (affected, PyPI) 3.29.5 (affected, PyPI) 3.29.6 (affected, PyPI) 3.29.7 (affected, PyPI) 3.30.0 (affected, PyPI) 3.30.1 (affected, PyPI) 3.30.2 (affected, PyPI) 3.30.3 (affected, PyPI) 3.31.0 (affected, PyPI) 3.31.1 (affected, PyPI) 3.31.2 (affected, PyPI) 3.32.0 (affected, PyPI) 3.32.2 (affected, PyPI) 3.32.3 (affected, PyPI) 3.32.4 (affected, PyPI) 3.32.5 (affected, PyPI) 3.32.6 (affected, PyPI) 3.32.7 (affected, PyPI) 4.0.0 (affected, PyPI) 4.0.1 (affected, PyPI) 4.0.10 (affected, PyPI) 4.0.11 (affected, PyPI) 4.0.12 (affected, PyPI) 4.0.2 (affected, PyPI) 4.0.3 (affected, PyPI) 4.0.4 (affected, PyPI) 4.0.5 (affected, PyPI) 4.0.6 (affected, PyPI) 4.0.7 (affected, PyPI) 4.0.8 (affected, PyPI) 4.0.9 (affected, PyPI) 4.1.0 (affected, PyPI) 4.1.1 (affected, PyPI) 4.1.2 (affected, PyPI) 4.2.0 (affected, PyPI) Ecosystem version events: introduced 3.20.4; fixed 4.2.1 Source events (ECOSYSTEM)Other versions: unaffected |
OSV GHSA-9vhv-jxww-xfm5 |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.1 / 3.3 low |
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L | CNA: GitHub_M |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5CNA: GitHub_M · x_refsource_CONFIRM
- https://github.com/tox-dev/filelock/pull/834CNA: GitHub_M · x_refsource_MISC
- https://github.com/tox-dev/filelock/pull/854CNA: GitHub_M · x_refsource_MISC
- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3bCNA: GitHub_M · x_refsource_MISC
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2dCNA: GitHub_M · x_refsource_MISC
- https://github.com/advisories/GHSA-9vhv-jxww-xfm5OSV / GitHub Security Advisories · advisory
- https://osv.dev/vulnerability/GHSA-9vhv-jxww-xfm5OSV / GitHub Security Advisories · osv
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.