Debian Package Tracker
Register | Log in
Subscribe

python-filelock

platform independent file locking module

Choose email to subscribe with

general
  • source: python-filelock (main)
  • version: 3.20.0-1
  • maintainer: Sascha Steinbiss (DMD) (LowNMU)
  • arch: all
  • std-ver: 4.7.2
  • VCS: Git (Browse, QA)
versions [more versions can be listed by madison] [old versions available from snapshot.debian.org]
[pool directory]
  • o-o-stable: 3.0.12-2
  • oldstable: 3.9.0-1
  • stable: 3.18.0-1
  • testing: 3.20.0-1
  • unstable: 3.20.0-1
versioned links
  • 3.0.12-2: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.9.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.18.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
  • 3.20.0-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
binaries
  • python3-filelock
action needed
1 security issue in trixie high

There is 1 open security issue in trixie.

1 important issue:
  • CVE-2025-68146: 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.
Created: 2025-12-16 Last update: 2025-12-17 05:32
1 security issue in sid high

There is 1 open security issue in sid.

1 important issue:
  • CVE-2025-68146: 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.
Created: 2025-12-16 Last update: 2025-12-17 05:32
1 security issue in forky high

There is 1 open security issue in forky.

1 important issue:
  • CVE-2025-68146: 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.
Created: 2025-12-16 Last update: 2025-12-17 05:32
1 security issue in bullseye high

There is 1 open security issue in bullseye.

1 important issue:
  • CVE-2025-68146: 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.
Created: 2025-12-16 Last update: 2025-12-17 05:32
1 security issue in bookworm high

There is 1 open security issue in bookworm.

1 important issue:
  • CVE-2025-68146: 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.
Created: 2025-12-16 Last update: 2025-12-17 05:32
A new upstream version is available: 3.20.1 high
A new upstream version 3.20.1 is available, you should consider packaging it.
Created: 2025-12-16 Last update: 2025-12-17 03:00
Multiarch hinter reports 1 issue(s) normal
There are issues with the multiarch metadata for this package.
  • python3-filelock could be marked Multi-Arch: foreign
Created: 2025-08-23 Last update: 2025-12-17 03:00
news
[rss feed]
  • [2025-10-16] python-filelock 3.20.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-10-11] Accepted python-filelock 3.20.0-1 (source) into unstable (Sascha Steinbiss)
  • [2025-08-28] python-filelock 3.19.1-1 MIGRATED to testing (Debian testing watch)
  • [2025-08-22] Accepted python-filelock 3.19.1-1 (source) into unstable (Sascha Steinbiss)
  • [2025-03-27] python-filelock 3.18.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-03-22] Accepted python-filelock 3.18.0-1 (source) into unstable (Sascha Steinbiss)
  • [2025-02-25] python-filelock 3.17.0-1 MIGRATED to testing (Debian testing watch)
  • [2025-02-19] Accepted python-filelock 3.17.0-1 (source) into unstable (Sascha Steinbiss)
  • [2025-02-15] Accepted python-filelock 3.16.1-2 (source) into unstable (Sascha Steinbiss)
  • [2024-10-15] python-filelock 3.16.1-1 MIGRATED to testing (Debian testing watch)
  • [2024-10-09] Accepted python-filelock 3.16.1-1 (source) into unstable (Sascha Steinbiss)
  • [2024-07-03] python-filelock 3.15.4-1 MIGRATED to testing (Debian testing watch)
  • [2024-06-27] Accepted python-filelock 3.15.4-1 (source) into unstable (Sascha Steinbiss)
  • [2024-05-08] python-filelock 3.14.0-1 MIGRATED to testing (Debian testing watch)
  • [2024-05-02] Accepted python-filelock 3.14.0-1 (source) into unstable (Sascha Steinbiss)
  • [2024-04-25] python-filelock 3.13.4-1 MIGRATED to testing (Debian testing watch)
  • [2024-04-20] Accepted python-filelock 3.13.4-1 (source) into unstable (Sascha Steinbiss)
  • [2024-04-11] python-filelock 3.13.3-1 MIGRATED to testing (Debian testing watch)
  • [2024-03-31] Accepted python-filelock 3.13.3-1 (source) into unstable (Sascha Steinbiss)
  • [2023-11-25] python-filelock 3.13.1-1 MIGRATED to testing (Debian testing watch)
  • [2023-11-20] Accepted python-filelock 3.13.1-1 (source) into unstable (Sascha Steinbiss)
  • [2023-09-25] python-filelock 3.12.4-1 MIGRATED to testing (Debian testing watch)
  • [2023-09-20] Accepted python-filelock 3.12.4-1 (source) into unstable (Sascha Steinbiss)
  • [2023-09-17] python-filelock 3.12.3-1 MIGRATED to testing (Debian testing watch)
  • [2023-09-12] Accepted python-filelock 3.12.3-1 (source) into unstable (Sascha Steinbiss)
  • [2023-06-20] python-filelock 3.12.2-1 MIGRATED to testing (Debian testing watch)
  • [2023-06-15] Accepted python-filelock 3.12.2-1 (source) into unstable (Sascha Steinbiss)
  • [2023-01-09] python-filelock 3.9.0-1 MIGRATED to testing (Debian testing watch)
  • [2023-01-02] Accepted python-filelock 3.9.0-1 (source) into unstable (Sascha Steinbiss)
  • [2022-12-16] python-filelock 3.8.2-1 MIGRATED to testing (Debian testing watch)
  • 1
  • 2
bugs [bug history graph]
  • all: 1
  • RC: 0
  • I&N: 1
  • M&W: 0
  • F&P: 0
  • patch: 0
links
  • homepage
  • lintian
  • buildd: logs, reproducibility
  • popcon
  • browse source code
  • edit tags
  • other distros
  • security tracker
  • screenshots
  • debci
ubuntu Ubuntu logo [Information about Ubuntu for Debian Developers]
  • version: 3.20.0-1

Debian Package Tracker — Copyright 2013-2025 The Distro Tracker Developers
Report problems to the tracker.debian.org pseudo-package in the Debian BTS.
Documentation — Bugs — Git Repository — Contributing