CVSS 3.1
6.1 mediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:LMedium (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.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:Lfilelock (PyPI): fixed in 4.2.1Explain 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.
From the NVD's CPE matches.
| Product | Affected |
|---|---|
| tox-dev:filelock | from 4.1.0 before 4.2.1 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-jqc4-5cvw-7w85 | PyPI | filelock | >=4.1.0 <4.2.1 | 4.2.1 |
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13 | python-filelock | no fix listed | DEBIAN-CVE-2026-112937 |
| Debian | 14 | python-filelock | 4.2.8-1 | DEBIAN-CVE-2026-112937 |
| Ubuntu | 26.04:LTS, 26.10, Pro:18.04:LTS and 3 more | python-filelock | no fix listed | UBUNTU-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 rates this Moderate.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.