Vulnerability · Published Oct 20, 2026 · Assigned by GitHub_M

CVE-2026-112914filelock: 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

In plain English

A medium-severity security flaw in filelock from tox-dev. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.2% (higher than 5% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.3Medium
Exploit odds (30 days)0.2%top 94.7% of all CVEs
Exploited in the wildNo reportsCISA SSVC: none
Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12python-filelockno fix listedDEBIAN-CVE-2026-112914
Debian:13python-filelockno fix listedDEBIAN-CVE-2026-112914
Debian:14python-filelockno fix listedDEBIAN-CVE-2026-112914
PyPIfilelock4.2.1GHSA-crv4-6mhj-j5jh
Ubuntu:26.04:LTSpython-filelockno fix listedUBUNTU-CVE-2026-112914
Ubuntu:26.10python-filelockno fix listedUBUNTU-CVE-2026-112914

Affected products (as reported)

VendorProductVersions
tox-dev filelock >= 4.1.0, < 4.2.1

Weakness: CWE-363 · Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N

References