Description
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock can open a crafted SQLite lock database without bounding schema and query work, allowing another local user who can replace the database to make acquisition stall or hang; versions from 3.20.4 expose this on initial per-instance opening, and versions from 3.30.0 repeat the exposure on every acquisition. This issue is fixed in version 4.2.1.
Published: 2026-10-20
Score: 5.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: Denial of Service through resource exhaustion
Action: Apply patch
AI Analysis

Impact

filelock is a cross‑platform file‑locking library for Python. In versions 3.20.4 through 4.2.0 the ReadWriteLock implementation opens a SQLite file lock database without bounding its schema or query work. A crafted database allows a local user, who can replace the database file, to cause every acquire operation to stall or hang regardless of any timeout. The result is a denial of service when processes attempt to obtain a lock, leading to resource exhaustion or unresponsive applications. This issue is fixed in version 4.2.1.

Affected Systems

The vulnerable product is the tox‑dev filelock library used in Python projects. All releases from 3.20.4 through 4.2.0 are affected. The issue is fixed in version 4.2.1. The vulnerability applies to any platform where the library is used since it relies on SQLite, and affects both local users and services running with elevated privileges that can write the lock database.

Risk and Exploitability

The CVSS base score is 5.5, indicating moderate severity. The EPSS score is 0.00218. The vulnerability is not listed in the CISA KEV catalog. The attack requires local user access to the directory holding the lock database. A local attacker who can replace the SQLite file can trigger a lock acquisition stall, making the affected process hang. Because the attack is local, the risk is limited to environments where the application runs with write access to the lock directory or where a malicious user can influence that path.

Generated by OpenCVE AI on October 22, 2026 at 20:43 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade the filelock library to version 4.2.1 or later.
  • If an upgrade is not possible, move the lock database to a location that is not writable by untrusted local users and ensure the permissions restrict write access.
  • Run services that use filelock under the least privilege principle, so that the process does not have permission to overwrite the lock database.

Generated by OpenCVE AI on October 22, 2026 at 20:43 UTC.

Tracking

Sign in to view the affected projects.

Advisories
Source ID Title
Github GHSA Github GHSA GHSA-cwqr-hh33-gh44 filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout
History

Wed, 21 Oct 2026 21:30:00 +0000

Type Values Removed Values Added
CPEs cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*

Wed, 21 Oct 2026 12:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-770
References
Metrics threat_severity

None

threat_severity

Moderate


Tue, 20 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
First Time appeared Tox-dev
Tox-dev filelock
Vendors & Products Tox-dev
Tox-dev filelock

Tue, 20 Oct 2026 16:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Tue, 20 Oct 2026 14:45:00 +0000

Type Values Removed Values Added
Description filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock can open a crafted SQLite lock database without bounding schema and query work, allowing another local user who can replace the database to make acquisition stall or hang; versions from 3.20.4 expose this on initial per-instance opening, and versions from 3.30.0 repeat the exposure on every acquisition. This issue is fixed in version 4.2.1.
Title filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout
Weaknesses CWE-400
References
Metrics cvssV3_1

{'score': 5.5, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'}


Subscriptions

Tox-dev Filelock
cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-20T15:25:38.592Z

Reserved: 2026-10-19T20:16:09.858Z

Link: CVE-2026-112915

cve-icon Vulnrichment

Updated: 2026-10-20T15:25:33.982Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-20T15:17:15.953

Modified: 2026-10-21T21:15:34.300

Link: CVE-2026-112915

cve-icon Redhat

Severity : Moderate

Publid Date: 2026-10-20T14:28:41Z

Links: CVE-2026-112915 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-22T20:45:05Z

Weaknesses
  • CWE-400

    Uncontrolled Resource Consumption

  • CWE-770

    Allocation of Resources Without Limits or Throttling