Vulnerability · Published Oct 20, 2026 · Assigned by GitHub_M

CVE-2026-112939filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable marker

Medium 4.7

In plain English

A medium-severity insufficient verification of data authenticity in filelock from tox-dev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 3% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)4.7Medium
Exploit odds (30 days)0.1%top 96.6% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can trust a forged process identifier in a marker that an attacker can modify but cannot remove, allowing an authorized contender such as another process of the holder's account or root to act as a confused deputy, remove the live marker, and admit another holder. This issue is fixed in version 4.2.1.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12python-filelockno fix listedDEBIAN-CVE-2026-112939
Debian:13python-filelockno fix listedDEBIAN-CVE-2026-112939
Debian:14python-filelockno fix listedDEBIAN-CVE-2026-112939
PyPIfilelock4.2.1GHSA-rfpc-qcw5-3pc4
Ubuntu:26.04:LTSpython-filelockno fix listedUBUNTU-CVE-2026-112939
Ubuntu:26.10python-filelockno fix listedUBUNTU-CVE-2026-112939

Affected products (as reported)

VendorProductVersions
tox-dev filelock >= 3.22.0, < 4.2.1

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

References