All vulnerabilities
CVE-2026-112936GHSA-j8f7-rjxc-mr56

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

tox-dev filelock
Open in ThreatlineRecord JSON
CVSS
6.1Medium
ExploitationPublic exploit codeCISA's assessment says proof of concept code is public, assessed 20 Oct 2026. Not in the KEV catalogCISA via CVE List
Exploit odds (EPSS)0.23%Chance of exploitation activity in the next 30 days, higher than 13% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in4.0.9Fixed versionGitHub
Published20 Oct 2026Updated 20 Oct 2026CVE List

What fixes it

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 2

  • filelockaffected: >= 3.20.4, < 4.0.9CVE List
  • filelock, pip>= 3.20.4, <= 4.0.8GitHub

References 3