CVE-2026-1129155.5MediumCWE-400

CVE-2026-112915: filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeout

tox-dev · filelock

Affected: tox-dev filelock · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.2%probability of exploitation in the next 30 days

12th percentile

050100

Higher than 12% of scored CVEs

5.5MediumCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

tox-dev · filelock>= 3.20.4, < 4.2.1

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Uncontrolled Resource Consumption · Denial of Service
Vendor: tox-dev
Published: October 2026
Band: Unlikely (under 1%), October 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-112915 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.