Skip to content
OpenAdvisories
High · 7.1 CVE-2026-112940 EUVD-2026-105031GHSA-v4x8-3wr5-3wq8

filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own files

Published Oct 20, 2026 · Updated Oct 22, 2026 · Assigned by GitHub_M

Description

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. This issue is fixed in version 4.2.1.

Affected products

VendorProductAffectedFixed
tox-dev filelock >= 3.20.4, < 4.2.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 python-filelock 4.2.8-1 —
Debian 13 python-filelock No fix yet —
Debian 12 python-filelock No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 python-filelock No fix yet —
Ubuntu 26.04 LTS python-filelock No fix yet —
Show 4 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro 24.04 LTS python-filelock No fix yet —
Ubuntu Pro 22.04 LTS python-filelock No fix yet —
Ubuntu Pro 20.04 LTS python-filelock No fix yet —
Ubuntu Pro 18.04 LTS python-filelock No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling open-webui 0.12.3-r10 —
Wolfi rolling py3-cassandra-medusa 0.31.0-r3 —
Wolfi rolling py3.10-filelock No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
PyPI filelock >= 3.20.4, < 4.2.1 4.2.1 GHSA-v4x8-3wr5-3wq8

References