Skip to content
OpenAdvisories
Medium · 6.1 CVE-2026-112937 EUVD-2026-105028GHSA-jqc4-5cvw-7w85

filelock: ReadWriteLock on the hard-link route deletes any directory another user renames onto its .filelock-* link directory name

Published Oct 20, 2026 · Updated Oct 21, 2026 · Assigned by GitHub_M

Description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized .filelock-* private-hard-link directory during cleanup, allowing another local user with rename access in a non-sticky parent to observe a live name or forge a dead-owner sweep name and rename a sibling directory onto it for deletion. This issue is fixed in version 4.2.1.

Affected products

VendorProductAffectedFixed
tox-dev filelock >= 4.1.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.8-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 >= 4.1.0, < 4.2.1 4.2.1 GHSA-jqc4-5cvw-7w85

References