Skip to content
OpenAdvisories
Medium · 5.3 CVE-2026-112908 EUVD-2026-117817GHSA-6627-m3xw-93mp

filelock: StrictSoftFileLock creates its claim directories without the lock mode, so another local user with a write bit on them can end a live hold

Published Nov 5, 2026 · Updated Nov 10, 2026 · Assigned by GitHub_M

Description

filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1,  StrictSoftFileLock  and  AsyncStrictSoftFileLock  on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1.

Affected products

VendorProductAffectedFixed
tox-dev filelock >= 3.30.0, < 4.2.1 —

Fixed in Linux distributions

Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.

ReleasePackageFixed inAdvisory
Debian 14 python-filelock 4.2.2-1 —
Debian 13 python-filelock No fix yet —
Debian 12 python-filelock No fix yet —
ReleasePackageFixed inAdvisory
Ubuntu 26.10 python-filelock No fix yet —
Ubuntu 26.04 LTS python-filelock No fix yet —
Show 4 more (older releases, extended support, other products)
ReleasePackageFixed inAdvisory
Ubuntu Pro 24.04 LTS python-filelock No fix yet —
Ubuntu Pro 22.04 LTS python-filelock No fix yet —
Ubuntu Pro 20.04 LTS python-filelock No fix yet —
Ubuntu Pro 18.04 LTS python-filelock No fix yet —

Wolfi

ReleasePackageFixed inAdvisory
Wolfi rolling py3.10-filelock No fix yet —

Affected packages

EcosystemPackageAffectedFixedRecord
PyPI filelock >= 3.30.0, < 4.2.1 4.2.1 GHSA-6627-m3xw-93mp

References