Approved changes feed: RSS · Atom

cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*

part: a version: * update: *

VendorTox Dev (6e485f1a-f301-5f7c-8685-bf5a9b836878)
ProductFilelock (6b085a26-1444-5bb0-9140-396b3a165dd0)
Edition*
Language*
Software edition*
Target softwarepython
Target hardware*
Other*

Notes

Imported from gcve-enriched-dumps CVE data

PURL mappings

PURLSourceLast updated
pkg:github/tox-dev/filelock purl2cpe 2026-11-03 09:58:46.341728
pkg:pypi/filelock purl2cpe 2026-11-03 09:58:46.341729

Vulnerability references

IdentifiercpeApplicabilitySubmitteddb.gcve.eu detailsRationale
CVE:CVE-2026-22701 vulnerable 2026-06-08 07:51:13.636544 filelock Time-of-Check-Time-of-Use (TOCTOU) Symlink Vulnerability in SoftFileLock
MEDIUM (5.3)
filelock is a platform-independent file lock for Python. Prior to version 3.20.3, a TOCTOU race condition vulnerability exists in the SoftFileLock implementation of the filelock package. An attacker with local filesystem access and permission to create symlinks can exploit a race condition between the permission validation and file creation to cause lock operations to fail or behave unexpectedly. The vulnerability occurs in the _acquire() method between raise_on_not_writable_file() (permission check) and os.open() (file creation). During this race window, an attacker can create a symlink at the lock file path, potentially causing the lock to operate on an unintended target file or leading to denial of service. This issue has been patched in version 3.20.3.
Published: 2026-01-10T05:59:28.872Z
Updated: 2026-01-12T16:45:50.638Z
Reference links
Imported from gcve-enriched-dumps CVE data
CVE:CVE-2025-68146 vulnerable 2026-06-08 07:41:20.876748 filelock has TOCTOU race condition that allows symlink attacks during lock file creation
MEDIUM (6.3)
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.
Published: 2025-12-16T18:10:54.599Z
Updated: 2025-12-17T18:51:00.794Z
Reference links
Imported from gcve-enriched-dumps CVE data

Contribute

You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.

Inspect record JSON

Open JSON directly

Open this panel to browse, search, copy or download the JSON record.