CVE-2026-112907

Description

filelock is a platform-independent file lock for Python. From 3.22.0 until 4.2.1, soft lock classes on Windows read an existing marker with _read_lock_file and remove a stale marker through break_lock_file using pathname operations that wait for an oplock break. Another local account with read access to an unheld marker can keep a Level 1 or batch oplock unanswered, causing SoftFileLock.acquire and related async or fallback locks to wait beyond timeout, blocking=False, and cancel_check. A stale marker under the oplock cannot be broken, but mutual exclusion remains intact and no file other than the marker is accessed. This issue is fixed in version 4.2.1.

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

Weakness

CISA SSVC decision points

Exploitationpoc
Automatableno
Technical impactpartial
Scored2026-11-10

Timeline

  1. 2026-10-23GitHub advisory published (GHSA-567q-5qvw-pf92)13 days before publication
  2. 2026-11-05Published by the CNA21:50 UTC
  3. 2026-11-10CISA SSVC decision recorded5 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-567q-5qvw-pf92, affected packages:

PackageVulnerable versionsFixed in
PyPI filelockfrom 3.22.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 filelock

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