CVE-2026-112941

What it is

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.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account. Limited direct impact.

Exploit odds

0.1% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2026-10-20 15:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-10-28 15:17 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.1% in the next 30 days (EPSS).
• Severity: 3.3 LOW (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2026-10-20 15:17 UTC

Last modified

2026-10-28 15:17 UTC

Exploit probability

0.1% · EPSS, next 30 days

Weakness

CWE-367

Record status

Modified

Affected

• tox-dev Filelock < 4.2.1

Attack profile CVSS 3.1 · 3.3

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-112941.md and follow it. Check whether this project is affected by CVE-2026-112941. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge