python-filelock - Debian Package Tracker

general

source: python-filelock (main)
version: 3.24.3-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
stable-p-u: 3.18.0-1+deb13u1
testing: 3.24.3-1
unstable: 3.24.3-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.18.0-1+deb13u1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]
3.24.3-1: [.dsc, use dget on this link to retrieve source package] [changelog] [copyright] [rules] [control]

binaries

python3-filelock

action needed

1 new commit since last upload, is it time to release? normal

vcswatch reports that this package seems to have new commits in its VCS but has not yet updated debian/changelog. You should consider updating the Debian changelog and uploading this new version into the archive.

Here are the relevant commit logs:

commit 6e5bb869132f8adcff87d711fac40e0e56689f2c
Author: Bastian Germann <bage@debian.org>
Date:   Mon Mar 2 11:49:04 2026 +0100

    Mark test dependencies

Created: 2026-03-02 Last update: 2026-03-02 12:02

1 low-priority security issue in trixie low

There is 1 open security issue in trixie.

1 issue left for the package maintainer to handle:

CVE-2026-22701: (needs triaging) 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.

You can find information about how to handle this issue in the security team's documentation.

1 issue that should be fixed with the next stable update:

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: 2026-01-10 Last update: 2026-02-28 11:30

2 low-priority security issues in bookworm low

There are 2 open security issues in bookworm.

2 issues left for the package maintainer to handle:

CVE-2025-68146: (needs triaging) 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.
CVE-2026-22701: (needs triaging) 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.

You can find information about how to handle these issues in the security team's documentation.

Created: 2025-12-16 Last update: 2026-02-28 11:30

Standards version of the package is outdated. wishlist

The package should be updated to follow the last version of Debian Policy (Standards-Version 4.7.3 instead of 4.7.2).

Created: 2025-12-23 Last update: 2026-02-21 15:32

news

[rss feed]

[2026-03-01] python-filelock 3.24.3-1 MIGRATED to testing (Debian testing watch)
[2026-02-21] Accepted python-filelock 3.24.3-1 (source) into unstable (Sascha Steinbiss)
[2026-01-18] python-filelock 3.20.3-1 MIGRATED to testing (Debian testing watch)
[2026-01-12] Accepted python-filelock 3.20.3-1 (source) into unstable (Sascha Steinbiss)
[2026-01-10] Accepted python-filelock 3.18.0-1+deb13u1 (source) into proposed-updates (Debian FTP Masters) (signed by: Sascha Steinbiss)
[2026-01-07] Accepted python-filelock 3.20.2-1 (source) into unstable (Sascha Steinbiss)
[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)

bugs [bug history graph]

all: 0

links

homepage
lintian
buildd: logs
popcon
browse source code
edit tags
other distros
security tracker
debci

ubuntu

[Information about Ubuntu for Debian Developers]

version: 3.20.3-1