Skip to content
OpenAdvisories
Medium · 6.1 CVE-2026-112934 EUVD-2026-105023GHSA-fj95-fr6c-h845

filelock: SoftReadWriteLock holder refresh writes through a hard link and hangs on a named pipe that another local user renames over its record

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

Description

filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1.

Affected products

VendorProductAffectedFixed
tox-dev filelock >= 4.0.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.0.0, < 4.2.1 4.2.1 GHSA-fj95-fr6c-h845

References