CVE-2026-112940 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

High 7.1 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-112940?

CVE-2026-112940 is a high-severity vulnerability in tox-dev filelock, published on 20 Oct 2026.

Official 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.

Weakness: CWE-59, CWE-363

Which versions are affected by CVE-2026-112940?

2 open source packages ship an affected version, including filelock. It affects 1 product.

PackageAffectedFixed in
filelock PyPIFrom 3.20.44.2.1
filelock PyPIFrom 3.20.44.2.1

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112940?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112940 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112940 exists.

Sources

Also known as CLEANSTART-2026-AE20147, DEBIAN-CVE-2026-112940, ECHO-a690-810d-47b0, GHSA-v4x8-3wr5-3wq8, MINI-qfrg-8m9x-cc2v, ROOT-APP-PYPI-CVE-2026-112940 and 1 more.

Is CVE-2026-112940 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free