CVE-2026-112912: filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock taker
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 11% of scored CVEs
DescriptionCVE.org
filelock is a platform-independent file lock for Python. From 3.32.6 until 4.2.1, SoftFileLock can follow a swapped symbolic link during the conditional os.access writability check for a node without its owner-write bit, allowing another local user on a platform and directory configuration that follows the link to infer whether a chosen path exists and is writable from the observable acquisition result. This issue is fixed in version 4.2.1.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- tox-dev · filelock>= 3.32.6, < 4.2.1
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-112912 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.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-59cwe.mitre.org
- github.com/tox-dev/filelock/security/advisories/GHSA-9j6q-wvj5-jgithub.com
- github.com/tox-dev/filelock/pull/835github.com
- github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5agithub.com
- github.com/tox-dev/filelock/releases/tag/4.2.1github.com