CVE-2026-112936: filelock: ReadWriteLock follows a symlink at the lock path into SQLite
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.
Higher than 14% of scored CVEs
DescriptionCVE.org
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 products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- tox-dev · filelock>= 3.20.4, < 4.0.9
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- tox-dev
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-112936 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.