CVE-2026-112909

Description

filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file renamed onto the lock path when another local user has actual rename permission, or hard-linked there under a permissive hard-link policy; when an explicit mode is requested, affected versions from 3.10.2 can also change that file's mode. 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:L/I:H/A:N · source cna
Exploit chance (EPSS)
0.220%
chance of exploitation in the next 30 days
higher than 12.7% 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-22

Timeline

  1. 2026-10-20Published by the CNA14:16 UTC
  2. 2026-10-22CISA SSVC decision recorded2 days after publication
  3. 2026-10-28GitHub advisory published (GHSA-69hj-f68j-2879)8 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-69hj-f68j-2879, affected packages:

PackageVulnerable versionsFixed in
PyPI filelockbefore 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 filelockbefore 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