All vulnerabilities
CVE-2026-112935GHSA-fq56-3cx3-fjxp

filelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holders

tox-dev filelock
Open in ThreatlineRecord JSON
CVSS
4.7Medium
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.10%Chance of exploitation activity in the next 30 days, higher than 0% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed inNone listedNo source names a fixed version. Check the vendor advisory below
Published20 Oct 2026Updated 20 Oct 2026CVE List

What fixes it

No source in this snapshot names a fixed version. The vendor advisories under References are the place to check.

Description

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, SoftFileLock can break a stale marker after an attacker frees its own marker following the stale read, an honest contender creates a live successor on the reused inode, and the successor's modification time is not newer than the saved observation, causing the live marker to be removed and two holders to be admitted. This issue is fixed in version 4.2.1.

Text from CVE List

Affected versions 1

  • filelockaffected: >= 3.22.0, < 4.2.1CVE List

References 4