CVE-2026-112940: filelock is a platform-independent file lock for Python
CVE-2026-112940 is a high-severity flaw (CVSS 7.1) affecting filelock. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those names to cause overwrite or unlink operations, while a writable adjacent hot journal is additionally required for attacker-chosen content overwrites. This issue is fixed in version 4.2.1.
Why this priority
- High severity
- Public exploit reference
A fixed release or distro patch exists.
Last updated 2026-10-22 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Exact fixes by distribution
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-112940?
filelock: upgrade to 4.2.1. Exact commands for each OS are on this page.
Is CVE-2026-112940 being exploited?
CVE-2026-112940 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-112940 affect?
CVE-2026-112940 affects filelock. Severity is high (CVSS 7.1). filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the database and side files by name; on POSIX systems an attacker with rename access in a non-sticky parent can swap those nam
How urgent is CVE-2026-112940?
Priority 30/100. High severity; Public exploit reference
Software pages
Python vulnerabilities · SQLite vulnerabilities
Related CVEs
- CVE-2026-112934 MEDIUM 6.1 UPGRADE filelock is a platform-independent file lock for Python