cve.bz

CVE-2026-112937 tox-dev filelock

6.1 mediumExploit referenceEPSS 0.2%Fix available

Medium (6.1) in tox-dev filelock. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in filelock 4.2.1.

On this page
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.

Severity

CVSS 3.1

6.1 medium
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:L
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 5th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-367 Time-of-check Time-of-use (TOCTOU) Race Condition
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-112937 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-112937?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-112937?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-112937 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
tox-dev:filelockfrom 4.1.0 before 4.2.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jqc4-5cvw-7w85PyPIfilelock>=4.1.0 <4.2.14.2.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13python-filelockno fix listedDEBIAN-CVE-2026-112937
Debian14python-filelock4.2.8-1DEBIAN-CVE-2026-112937
Ubuntu26.04:LTS, 26.10, Pro:18.04:LTS and 3 morepython-filelockno fix listedUBUNTU-CVE-2026-112937

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

This vulnerability is rated as Moderate severity because exploitation requires local access under specific non-standard deployment conditions, despite carrying a significant integrity risk of directory deletion. On standard Red Hat Enterprise Linux environments where the /proc filesystem is mounted, filelock employs descriptor-based locking and does not trigger the affected cleanup routine. The risk is primarily restricted to custom container or chroot setups lacking /proc where lock files reside within shared, non-sticky directories accessible to untrusted local users.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-112937.

Attack patterns (CAPEC)

  • CAPEC-27 Leveraging Race Conditions via Symbolic Links Likelihood: Medium · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON