CVE-2026-112941 filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock

Low 3.3 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-112941?

CVE-2026-112941 is a low-severity vulnerability in tox-dev filelock, published on 20 Oct 2026.

Official description

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftReadWriteLock and AsyncSoftReadWriteLock cache a successful check of the <path>.rw lock tree and resolve its names again during later record operations, allowing another local user who can replace that tree after the first acquisition to redirect lock-record writes into directories writable by the lock user. This issue is fixed in version 4.2.1.

Weakness: CWE-367

Which versions are affected by CVE-2026-112941?

2 open source packages ship an affected version, including filelock. It affects 1 product.

PackageAffectedFixed in
filelock PyPIFrom 4.1.04.2.1
filelock PyPIFrom 4.1.04.2.1

Products include Tox-Dev Filelock.

How do I fix CVE-2026-112941?

Upgrade filelock to 4.2.1 or later.

Is CVE-2026-112941 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-112941 exists.

Sources

Also known as DEBIAN-CVE-2026-112941, GHSA-wfhq-q4j2-c37m, UBUNTU-CVE-2026-112941.

Is CVE-2026-112941 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free