CVE-2026-112914 filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory

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

What is CVE-2026-112914?

CVE-2026-112914 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 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. This issue is fixed in version 4.2.1.

Weakness: CWE-59, CWE-363

Which versions are affected by CVE-2026-112914?

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

PackageAffectedFixed in
filelock PyPIFrom 4.1.04.2.1
filelock PyPIFrom 4.1.04.2.1

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112914?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112914 being exploited?

There is no known exploitation of CVE-2026-112914 in the wild and no public exploit code.

Sources

Also known as DEBIAN-CVE-2026-112914, ECHO-d985-2000-8340, GHSA-crv4-6mhj-j5jh, UBUNTU-CVE-2026-112914.

Is CVE-2026-112914 in your software?

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

Check your SBOMs for free