CVE-2026-112936 filelock: ReadWriteLock follows a symlink at the lock path into SQLite

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

What is CVE-2026-112936?

CVE-2026-112936 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.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory to redirect database creation and locking or split mutual exclusion between targets. This issue is fixed in version 4.0.9.

Weakness: CWE-668, CWE-59

Which versions are affected by CVE-2026-112936?

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

PackageAffectedFixed in
filelock PyPIFrom 3.20.44.0.9
filelock PyPIFrom 3.20.44.0.9

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112936?

Upgrade filelock to 4.0.9 or later.

Is CVE-2026-112936 being exploited?

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

Sources

Also known as CLEANSTART-2026-WN99561, DEBIAN-CVE-2026-112936, GHSA-j8f7-rjxc-mr56, MINI-6h74-9xmh-247x, UBUNTU-CVE-2026-112936.

Is CVE-2026-112936 in your software?

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

Check your SBOMs for free