Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-112914: filelock is a platform-independent file lock for Python

25
Routine
MEDIUM 5.3UPGRADE

CVE-2026-112914 is a medium-severity flaw (CVSS 5.3) 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 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in a symbolic link and, on a runtime that follows the link and a same-filesystem target, make the lock user hard-link one of its files into the lock directory. This issue is fixed in version 4.2.1.

Why this priority

  • Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score5.3 (Medium)
Attack vectorLocal
Attack complexityHigh
Privileges neededLow
User interactionNone
EPSS exploit chance0.2% (top 95%)
CISA exploited listNo
WeaknessCWE-363, CWE-59
Published2026-10-20
Last modified2026-10-21
Publisher (CNA): GitHub, Inc. · Vendor: tox-dev

Share: LinkedIn · X · Reddit

Last updated 2026-10-21 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

tox-dev filelock UPGRADE
Affected: >= 4.1.0 and < 4.2.1
Fixed in: 4.2.1
Safe to downgrade to: a release before 4.1.0
1. Check installed version
pip show filelock
2. UPGRADE to 4.2.1
pip install --upgrade "filelock>=4.2.1"
3. If no update is available yet, DOWNGRADE to a release before 4.1.0
pip index versions filelock pip install "filelock<4.1.0"
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
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-112914?

filelock: upgrade to 4.2.1. Exact commands for each OS are on this page.

Is CVE-2026-112914 being exploited?

CVE-2026-112914 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-112914 affect?

CVE-2026-112914 affects filelock. Severity is medium (CVSS 5.3). filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock can restore a stale marker by name after moving it aside, allowing another local user with rename access in a non-sticky lock directory to swap in

How urgent is CVE-2026-112914?

Priority 25/100. Public exploit reference

Software pages

Python vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.