# CVE-2026-112913: filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its database

Status: published. Published: 2026-11-05. Updated: 2026-11-05.

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.

## Remediation

- fix: filelock (PyPI): OSV reports a fixed version 4.2.1. Check the advisory for supported release branches. (source: OSV GHSA-9vhv-jxww-xfm5) — https://github.com/advisories/GHSA-9vhv-jxww-xfm5

## Affected products and versions

- tox-dev / filelock: >= 3.20.4, < 4.2.1 (affected). Source: CNA: GitHub_M
-  / filelock (filelock): 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: OSV GHSA-9vhv-jxww-xfm5

## Severity and prioritization

- CVSS 3.1: 3.3 (low); CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L; source: CNA: GitHub_M

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-367

## 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-xfm5 (CNA: GitHub_M; x_refsource_CONFIRM)

- https://github.com/tox-dev/filelock/pull/834 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/tox-dev/filelock/pull/854 (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d (CNA: GitHub_M; x_refsource_MISC)

- https://github.com/advisories/GHSA-9vhv-jxww-xfm5 (OSV / GitHub Security Advisories; advisory)

- https://osv.dev/vulnerability/GHSA-9vhv-jxww-xfm5 (OSV / GitHub Security Advisories; osv)

## Provenance

- CNA: GitHub_M: https://www.cve.org/CVERecord?id=CVE-2026-112913; retrieved 2026-11-05; source updated 2026-11-05

- OSV / GitHub Security Advisories: https://osv.dev/vulnerability/GHSA-9vhv-jxww-xfm5; retrieved 2026-11-05; source updated 2026-10-23

Revision: e7c4117df847915079016d9e7a46b4ec0736b6f3867e4ff48a54431db635c13e

Canonical: https://y2.dev/cve/CVE-2026-112913

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.