CVE-2026-112910

NameCVE-2026-112910
Descriptionfilelock is a platform-independent file lock for Python. From 3.10.0 until 4.2.1, filelock on Windows ignores the mode argument for WindowsFileLock files and the ReadWriteLock SQLite database. A lock created with mode=0o600 receives the parent directory's inheritable ACL because _open_non_reparse_fd and _nt_open do not create an owner-only security descriptor. Another local account with inherited access can read holder metadata or the lock database, modify those files where the ACL permits writes, or take the byte-range lock after release and delay later acquisitions. UnixFileLock is not affected, and mutual exclusion between cooperating processes continues to hold. 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-8mx5-7m5m-r77g
https://github.com/tox-dev/filelock/pull/835
Fixed by: https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a (4.2.1)

Search for package or bug name: Reporting problems