Skip to content
Noroxi
CVE-2025-68146· NVD / CVE Program· CNA GitHub_M

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

filelock is a platform-independent file lock for Python. In versions prior to 3.20.1, a Time-of-Check-Time-of-Use (TOCTOU) race condition allows local attackers to corrupt or truncate arbitrary user files through symlink attacks. The vulnerability exists in both Unix and Windows lock file creation where filelock checks if a file exists before opening it with O_TRUNC. An attacker can create a symlink pointing to a victim file in the time gap between the check and open, causing os.open() to follow the symlink and truncate the target file. All users of filelock on Unix, Linux, macOS, and Windows systems are impacted. The vulnerability cascades to dependent libraries. The attack requires local filesystem access and ability to create symlinks (standard user permissions on Unix; Developer Mode on Windows 10+). Exploitation succeeds within 1-3 attempts when lock file paths are predictable. The issue is fixed in version 3.20.1. If immediate upgrade is not possible, use SoftFileLock instead of UnixFileLock/WindowsFileLock (note: different locking semantics, may not be suitable for all use cases); ensure lock file directories have restrictive permissions (chmod 0700) to prevent untrusted users from creating symlinks; and/or monitor lock file directories for suspicious symlinks before running trusted applications. These workarounds provide only partial mitigation. The race condition remains exploitable. Upgrading to version 3.20.1 is strongly recommended.

MediumCVSS 6.5 · v3.1—No exploit Fix available
Published
Dec 16, 2025
Updated
Jun 17, 2026
EPSS
0.2% · 9th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

26

Monitor

Low priority for now.

CVSS
26 / 40 · 6.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.2%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
6.5
CNA · GitHub_M
6.3
0.2 point gap

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
tox-devfilelock

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • tox-dev filelockbefore 3.20.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • tox-dev filelock

    • < 3.20.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12python-filelockbefore 3.9.0-1+deb12u13.9.0-1+deb12u1
Debian:13python-filelockbefore 3.18.0-1+deb13u13.18.0-1+deb13u1
Debian:14python-filelockbefore 3.20.2-13.20.2-1
openSUSE:Leap 16.0python-filelockbefore 3.18.0-160000.3.13.18.0-160000.3.1
openSUSE:Tumbleweedpython-filelockbefore 3.20.2-1.13.20.2-1.1
openSUSE:Tumbleweedpython-virtualenvbefore 20.36.1-1.120.36.1-1.1
PyPIfilelockbefore 3.20.13.20.1
SUSE:Linux Enterprise Module for Development Tools 15 SP7python-filelockbefore 3.0.12-150100.3.6.13.0.12-150100.3.6.1
SUSE:Linux Enterprise Module for Python 3 15 SP7python-filelockbefore 3.12.2-150400.10.8.13.12.2-150400.10.8.1
SUSE:Linux Enterprise Module for Python 3 15 SP7python-filelockbefore 3.12.2-150400.10.8.13.12.2-150400.10.8.1
SUSE:Linux Enterprise Server 16.0python-filelockbefore 3.18.0-160000.3.13.18.0-160000.3.1

Other highest-scoring records for the same primary product.

  • CVE-2026-22701filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
tox-dev filelock3.20.1 · descriptionVendor (CNA)
debian:python-filelock3.9.0-1+deb12u1 · Debian:12Package registry (OSV)
opensuse:python-filelock3.12.2-150400.10.8.1 · openSUSE:Leap 15.6Package registry (OSV)
opensuse:python-virtualenv20.36.1-1.1 · openSUSE:TumbleweedPackage registry (OSV)
PyPI:filelock3.20.1Package registry (OSV)
suse:python-filelock3.0.12-150100.3.6.1 · SUSE:Linux Enterprise Module for Development Tools 15 SP7Package registry (OSV)
suse:python-filelock3.12.2-150400.10.8.1 · SUSE:Linux Enterprise Module for Python 3 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-2270125 days apartfilelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock
    21Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
low · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality impact
Low
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:H

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records