CVE-2026-112909 filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock path

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

What is CVE-2026-112909?

CVE-2026-112909 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. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. This issue is fixed in version 4.2.1.

Weakness: CWE-706

Which versions are affected by CVE-2026-112909?

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

PackageAffectedFixed in
filelock PyPIAll versions4.2.1
filelock PyPIAll versions4.2.1

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112909?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112909 being exploited?

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

Sources

Also known as AZL-110067, CLEANSTART-2026-ZN36596, DEBIAN-CVE-2026-112909, GHSA-69hj-f68j-2879, MINI-5vrg-6385-j6xg, MINI-vmj9-r77g-8m2h and 1 more.

Is CVE-2026-112909 in your software?

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

Check your SBOMs for free