CVE-2026-112906

Description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.

Severity
MEDIUM
CVSS v3
4.7
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N · source cna
Exploit chance (EPSS)
0.168%
chance of exploitation in the next 30 days
higher than 6.2% of scored CVEs · 2026-11-17
CISA KEV
Not listed
Public exploit code
Yes
Exploit references (NVD and CNA): 1
Metasploit modules: 0
Nuclei templates: 0

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-10-20

Timeline

  1. 2026-10-20Published by the CNA14:09 UTC
  2. 2026-10-20CISA SSVC decision recordedsame day
  3. 2026-10-23GitHub advisory published (GHSA-2g95-wg33-c5x2)3 days after publication

The timeline shows what already happened. To be told when this CVE changes next, watch it from the API.

Exploit and advisory records

GitHub advisory GHSA-2g95-wg33-c5x2, affected packages:

PackageVulnerable versionsFixed in
PyPI filelockfrom 4.1.0 before 4.2.14.2.1

Affected products

Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.

ProductVulnerable versionsFixed in
tox-dev filelockfrom 4.1.0 before 4.2.1fixed in 4.2.14.2.1

Products and versions as NVD and the vendor that published the CVE list them.

References

Get more CVE data from the API.

Free without a key or signup. Pro adds monitoring and higher limits: pricing.

Sources