Vulnerability · Published Oct 20, 2026 · Assigned by GitHub_M

CVE-2026-112911filelock: StrictSoftFileLock and SoftReadWriteLock adopt a protocol directory another user created first, losing mutual exclusion

Medium 6.3

In plain English

A medium-severity security flaw in filelock from tox-dev. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.1% (higher than 4% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)6.3Medium
Exploit odds (30 days)0.1%top 96.0% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack toolingNoneno public tooling known

Official description

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from 3.30.0 and SoftReadWriteLock versions from 4.0.0 can adopt a protocol directory created first by another local user in a shared parent directory, allowing that user to alter protocol state and admit concurrent holders. This issue is fixed in version 4.2.1.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12python-filelockno fix listedDEBIAN-CVE-2026-112911
Debian:13python-filelockno fix listedDEBIAN-CVE-2026-112911
Debian:14python-filelockno fix listedDEBIAN-CVE-2026-112911
PyPIfilelock4.2.1GHSA-9c4x-gm8v-wgc4
Ubuntu:26.04:LTSpython-filelockno fix listedUBUNTU-CVE-2026-112911
Ubuntu:26.10python-filelockno fix listedUBUNTU-CVE-2026-112911

Affected products (as reported)

VendorProductVersions
tox-dev filelock >= 3.30.0, < 4.2.1

Weakness: CWE-283 · Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H

References