CVE-2026-112915 filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout

Medium 5.5 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-112915?

CVE-2026-112915 is a medium-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 can open a crafted SQLite lock database without bounding schema and query work, allowing another local user who can replace the database to make acquisition stall or hang; versions from 3.20.4 expose this on initial per-instance opening, and versions from 3.30.0 repeat the exposure on every acquisition. This issue is fixed in version 4.2.1.

Weakness: CWE-400

Which versions are affected by CVE-2026-112915?

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-112915?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112915 being exploited?

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

Sources

Also known as CLEANSTART-2026-WY72270, DEBIAN-CVE-2026-112915, GHSA-cwqr-hh33-gh44, MINI-wvpx-f7ph-p3c9, UBUNTU-CVE-2026-112915.

Is CVE-2026-112915 in your software?

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

Check your SBOMs for free