CISA list

● PyPI package

filelock

Filelock has 20 security advisories. The newest release any of them names as the fix is 4.2.1.

As of , filelock has 20 security advisories. The newest release any of them names as the fix is 4.2.1.

Your version, and the version to upgrade to

Find the row your installed version falls in. The second column is the first release after it that none of the advisories lists as affected; a release outside every row is one no advisory lists. That is what the advisories say, not a promise that a release is free of flaws.
If you runUpgrade toAdvisories
Before 4.2.14.2.120 advisories

Security advisories, newest first

Security advisories, newest first
AdvisoryWhat it isAffectsFixed inPublished
CVE-2026-112941GHSA-wfhq-q4j2-c37mfilelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lockLow severityFrom 4.1.0 before 4.2.14.2.1
CVE-2026-112908GHSA-6627-m3xw-93mpfilelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live holdModerate severityFrom 3.30.0 before 4.2.14.2.1
CVE-2026-112911GHSA-9c4x-gm8v-wgc4filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusionModerate severityFrom 3.30.0 before 4.2.14.2.1
CVE-2026-112910GHSA-8mx5-7m5m-r77gfilelock: WindowsFileLock ignores mode: a 0o600 lock file and the ReadWriteLock database inherit the directory ACLModerate severityFrom 3.10.0 before 4.2.14.2.1
CVE-2026-112915GHSA-cwqr-hh33-gh44filelock ReadWriteLock: a crafted lock database makes every acquire stall or hang regardless of timeoutModerate severityFrom 3.20.4 before 4.2.14.2.1
CVE-2026-112939GHSA-rfpc-qcw5-3pc4filelock: SoftFileLock removes a live holder's marker when another user forges the PID in a writable markerModerate severityFrom 3.22.0 before 4.2.14.2.1
CVE-2026-112912GHSA-9j6q-wvj5-jgjgfilelock: Symlink swap during SoftFileLock's writability check leaks whether a path exists and is writable by the lock takerLow severityFrom 3.32.6 before 4.2.14.2.1
CVE-2026-112909GHSA-69hj-f68j-2879filelock: UnixFileLock truncates and chmods any regular file another user renames or hard-links onto the lock pathModerate severityBefore 4.2.14.2.1
CVE-2026-112936GHSA-j8f7-rjxc-mr56filelock: ReadWriteLock follows a symlink at the lock path into SQLiteModerate severityFrom 3.20.4 before 4.0.94.0.9
CVE-2026-112938GHSA-m462-7rxw-wvpgfilelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user choosesModerate severityFrom 3.30.0 before 4.2.14.2.1
CVE-2026-112934GHSA-fj95-fr6c-h845filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its recordModerate severityFrom 4.0.0 before 4.2.14.2.1
CVE-2026-112935GHSA-fq56-3cx3-fjxpfilelock: SoftFileLock stale-lock break removes a live lock file on a reused inode number and admits two holdersModerate severityFrom 3.22.0 before 4.2.14.2.1
CVE-2026-112937GHSA-jqc4-5cvw-7w85filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory nameModerate severityFrom 4.1.0 before 4.2.14.2.1
CVE-2026-112913GHSA-9vhv-jxww-xfm5filelock: ReadWriteLock on Windows acts on SQLite side files another local user places beside its databaseLow severityFrom 3.20.4 before 4.2.14.2.1
CVE-2026-112907GHSA-567q-5qvw-pf92filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale breakLow severityFrom 3.22.0 before 4.2.14.2.1
CVE-2026-112906GHSA-2g95-wg33-c5x2filelock: SoftFileLock evicts a fresh lock file whose watched age another local user's pre-dated file passed on through inode reuseModerate severityFrom 4.1.0 before 4.2.14.2.1
CVE-2026-112914GHSA-crv4-6mhj-j5jhfilelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directoryModerate severityFrom 4.1.0 before 4.2.14.2.1
CVE-2026-112940GHSA-v4x8-3wr5-3wq8filelock ReadWriteLock: SQLite reopens the lock database by name, so a planted symlink or journal file makes the lock user's process overwrite or unlink its own filesHigh severityFrom 3.20.4 before 4.2.14.2.1
CVE-2026-22701GHSA-qmgc-5h2g-mvrw, PYSEC-2026-1374filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLockModerate severityBefore 3.20.33.20.3
CVE-2025-68146GHSA-w853-jp5j-5j7f, PYSEC-2026-1375filelock has a TOCTOU race condition which allows symlink attacks during lock file creationModerate severityBefore 3.20.13.20.1

Other PyPI packages

Sources
  • Package advisories from the GitHub Advisory Database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0
  • Package advisories from the PyPA advisory database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0