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

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

What is CVE-2026-112939?

CVE-2026-112939 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.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.

Weakness: CWE-345

Which versions are affected by CVE-2026-112939?

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

PackageAffectedFixed in
filelock PyPIFrom 3.22.04.2.1
filelock PyPIFrom 3.22.04.2.1

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112939?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112939 being exploited?

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

Sources

Also known as CLEANSTART-2026-AU42206, DEBIAN-CVE-2026-112939, GHSA-rfpc-qcw5-3pc4, MINI-grpq-3wj4-6jwp, UBUNTU-CVE-2026-112939.

Is CVE-2026-112939 in your software?

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

Check your SBOMs for free