Advisory record · GHSA-w853-jp5j-5j7f

filelock has a TOCTOU race condition which allows symlink attacks during lock file creation

CVSS 6.3 MediumEPSS 0.0021 · 11th percentile

Published by the GitHub Advisory Database at 16 Dec 2025, 20:52 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
filelockPyPI<3.20.13.20.1
Identifiers
GHSA-w853-jp5j-5j7f · CVE-2025-68146 · PYSEC-2026-1375
Weakness (CWE)
CWE-59 · CWE-362 · CWE-367
Published
16 Dec 2025
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The filelock Python package (PyPI) versions before 3.20.1 are affected by a time-of-check-time-of-use race during lock file creation on Unix and Windows. A local user who can create symlinks can point a lock file path at another file in the gap between the existence check and the open, causing that file to be truncated. Upgrade to filelock 3.20.1 or later. Restricting write access to lock file directories reduces exposure but does not fully mitigate the issue.

Written 5 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
6.3 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 11th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.