CVE-2026-112936

filelock: ReadWriteLock follows a symlink at the lock path into SQLite

MEDIUM
6.1
CVSS Score
Published: October 20, 2026 at 02:34 PM UTC
Updated: October 21, 2026 at 06:09 PM UTC
1 product affected across 1 vendorFilelock

Using filelock by tox-dev?

Get instant alerts when new vulnerabilities affect filelock - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.1
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock versions from 3.20.4 resolve the lock path and pass it to SQLite without rejecting a final symbolic link, allowing another local user who can create names in the lock directory to redirect database creation and locking or split mutual exclusion between targets. This issue is fixed in version 4.0.9.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

3.20.4 ≤ v < 4.0.9

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (3)

x_refsource_CONFIRMExploitVendor Advisory
Source: cverecord
https://github.com/tox-dev/filelock/security/advisories/GHSA-j8f7-rjxc-mr56
x_refsource_MISCRelease Notes
Source: cverecord
https://github.com/tox-dev/filelock/releases/tag/4.0.9

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

6.1MEDIUMGitHub_M
Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
HIGH
Availability
LOW
Vector?

Quick Info

StatusANALYZED
CWE
CWE-59CWE-668

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card