CVE-2026-112937

Description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.

Severity
MEDIUM
CVSS v3
6.1
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L · source cna
Exploit chance (EPSS)
0.162%
chance of exploitation in the next 30 days
higher than 5.4% 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

Exploitationnone
Automatableno
Technical impactpartial
Scored2026-10-21

Timeline

  1. 2026-10-20Published by the CNA14:36 UTC
  2. 2026-10-21CISA SSVC decision recorded1 day after publication
  3. 2026-10-23GitHub advisory published (GHSA-jqc4-5cvw-7w85)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-jqc4-5cvw-7w85, 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