Technology · PyPI
filelock (PyPI) vulnerabilities
Updated . Rebuilt every hour.
Junglewise Threat Intelligence has tracked 20 vulnerabilities in filelock (PyPI): 0 in the last 7 days and 18 in the last 90 days, 0 of them critical and 0 exploited in the wild. The most recent, CVE-2026-112938, was published on 5 November 2026. 18 vulnerabilities in the last four weeks, up from none in the four before.
- Last 7 days
- 0
- Last 90 days
- 18
- Critical, all time
- 0
- Exploited in the wild
- 0
About filelock (PyPI)
A file-based lock mechanism for synchronizing file access across processes.
Latest filelock (PyPI) vulnerabilities
- CVE-2026-112938: filelock StrictSoftFileLock symlink race privilege escalationmediumCVSS 5.8
- CVE-2026-112913: filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its databaselowCVSS 3.3
- CVE-2026-112910: filelock WindowsFileLock mode parameter permission enforcement failuremediumCVSS 5.3
- CVE-2026-112908: filelock StrictSoftFileLock directory permission bypassmediumCVSS 5.3
- CVE-2026-112907: filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale…lowCVSS 3.1
- CVE-2026-112941: filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and…lowCVSS 3.3EPSS 0.1%
- CVE-2026-112940: filelock ReadWriteLock SQLite database overwrite in POSIXhighCVSS 7.1EPSS 0.2%
- CVE-2026-112939: filelock SoftFileLock PID spoofing privilege escalationmediumCVSS 4.7EPSS 0.1%
- CVE-2026-112937: filelock ReadWriteLock insecure temporary directory cleanupmediumCVSS 6.1EPSS 0.2%
- CVE-2026-112936: filelock ReadWriteLock symlink following vulnerabilitymediumCVSS 6.1EPSS 0.2%
- CVE-2026-112935: filelock SoftFileLock file lock bypassmediumCVSS 4.7EPSS 0.1%
- CVE-2026-112934: filelock SoftReadWriteLock directory traversal and lock stallingmediumCVSS 6.1EPSS 0.2%
- CVE-2026-112915: filelock ReadWriteLock unbounded SQLite query denial of servicemediumCVSS 5.5EPSS 0.2%
- CVE-2026-112914: filelock SoftFileLock symlink attack via stale markermediumCVSS 5.3EPSS 0.2%
- CVE-2026-112912: filelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock…lowCVSS 3.1EPSS 0.2%
- CVE-2026-112911: filelock StrictSoftFileLock directory adoption vulnerabilitymediumCVSS 6.3EPSS 0.1%
- CVE-2026-112909: filelock UnixFileLock file truncation on renamemediumCVSS 6.1EPSS 0.2%
- CVE-2026-112906: filelock SoftFileLock stale marker reuse race conditionmediumCVSS 4.7EPSS 0.2%
- CVE-2026-22701: PYSEC-2026-1374 - filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLocklowCVSS 3.1EPSS 0.1%
- CVE-2025-68146: PYSEC-2026-1375 - filelock has a TOCTOU race condition which allows symlink attacks during lock file creationlowCVSS 3.1EPSS 0.2%
Most severe filelock (PyPI) vulnerabilities
Exploited in the wild first, then by severity and CVSS score.
- CVE-2026-112940: filelock ReadWriteLock SQLite database overwrite in POSIXhighCVSS 7.1EPSS 0.2%
- CVE-2026-112911: filelock StrictSoftFileLock directory adoption vulnerabilitymediumCVSS 6.3EPSS 0.1%
- CVE-2026-112936: filelock ReadWriteLock symlink following vulnerabilitymediumCVSS 6.1EPSS 0.2%
- CVE-2026-112934: filelock SoftReadWriteLock directory traversal and lock stallingmediumCVSS 6.1EPSS 0.2%
- CVE-2026-112909: filelock UnixFileLock file truncation on renamemediumCVSS 6.1EPSS 0.2%
- CVE-2026-112937: filelock ReadWriteLock insecure temporary directory cleanupmediumCVSS 6.1EPSS 0.2%
- CVE-2026-112938: filelock StrictSoftFileLock symlink race privilege escalationmediumCVSS 5.8
- CVE-2026-112915: filelock ReadWriteLock unbounded SQLite query denial of servicemediumCVSS 5.5EPSS 0.2%
- CVE-2026-112914: filelock SoftFileLock symlink attack via stale markermediumCVSS 5.3EPSS 0.2%
- CVE-2026-112910: filelock WindowsFileLock mode parameter permission enforcement failuremediumCVSS 5.3
Vulnerabilities per week
18 vulnerabilities in the last four weeks, up from none in the four before. The last 13 weeks, by the week each vulnerability was published.
| Week of | Bar | Vulns | Critical |
|---|---|---|---|
| 17 Aug 2026 | 0 | 0 | |
| 24 Aug 2026 | 0 | 0 | |
| 31 Aug 2026 | 0 | 0 | |
| 7 Sep 2026 | 0 | 0 | |
| 14 Sep 2026 | 0 | 0 | |
| 21 Sep 2026 | 0 | 0 | |
| 28 Sep 2026 | 0 | 0 | |
| 5 Oct 2026 | 0 | 0 | |
| 12 Oct 2026 | 0 | 0 | |
| 19 Oct 2026 | 13 | 0 | |
| 26 Oct 2026 | 0 | 0 | |
| 2 Nov 2026 | 5 | 0 | |
| 9 Nov 2026 | 0 | 0 |
Embed a badge
A live badge for a README, a status page or an internal wiki: how many filelock (PyPI) vulnerabilities were published in the last 7 days and how many of them are critical, refreshed hourly.
[](https://junglewise.ai/threats/technologies/filelock)<a href="https://junglewise.ai/threats/technologies/filelock"><img src="https://junglewise.ai/threats/technologies/filelock/badge.svg" alt="filelock (PyPI) vulnerabilities" /></a>How this is built
Junglewise Threat Intelligence collects vulnerabilities from NVD, GitHub Security Advisories, OSV, the CISA Known Exploited Vulnerabilities catalog, FIRST EPSS and vendor advisories, and matches each one to the technologies and vendors it affects. Dates are the date a vulnerability was published, in UTC.
The pages are rebuilt from the database every hour. Frozen weekly and monthly reports never change once published, so they can be cited.
Use this data
The same data is at https://junglewise.ai/threats/technologies/filelock.json, and this page as text at https://junglewise.ai/threats/technologies/filelock.md, for scripts and language models. It is free to reuse under CC BY 4.0 with a link back to this page.
Cite as: Junglewise Threat Intelligence, "filelock (PyPI) vulnerabilities", https://junglewise.ai/threats/technologies/filelock, 13 November 2026.