CVE-2026-112937

MEDIUMCVSS 6.1/10EPSS 0.09%

Last modified

CVE-2026-112937 is a medium-severity vulnerability rated 6.1/10 on the CVSS scale. 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. EPSS estimates a 0.09% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.09%

0.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
Tox-DevFilelock>= 4.1.0, < 4.2.1

References

Timeline

Published
Last Modified
Status
Analyzed

Frequently Asked Questions

What is CVE-2026-112937?
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.
How severe is CVE-2026-112937?
CVE-2026-112937 has a CVSS score of 6.1/10 (MEDIUM severity). The EPSS model estimates a 0.09% probability of exploitation in the next 30 days.
How do I fix CVE-2026-112937?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

Are you affected by CVE-2026-112937?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST