CVE-2026-112913

NameCVE-2026-112913
Descriptionfilelock 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.
SourceCVE (at NVD; CERT, ENISA, LWN, oss-sec, fulldisc, Debian ELTS, Red Hat, Ubuntu, Gentoo, SUSE bugzilla/CVE, GitHub advisories/code/issues, web search, more)

Vulnerable and fixed packages

The table below lists information on source packages.

Source PackageReleaseVersionStatus
python-filelock (PTS)bookworm3.9.0-1+deb12u1fixed
trixie3.18.0-1+deb13u1fixed
forky4.1.1-1fixed
sid4.2.8-1fixed

The information below is based on the following data on fixed versions.

PackageTypeReleaseFixed VersionUrgencyOriginDebian Bugs
python-filelocksource(unstable)(not affected)

Notes

- python-filelock <not-affected> (Only affects filelock module on Windows)
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
Fixed by: https://github.com/tox-dev/filelock/commit/5e3f2ec0c5fb17cb2635b60b2b68bc63ab81ca2d (4.2.1)

Search for package or bug name: Reporting problems