Finding and attribution
On the private hard-link route, filelock recursively removes a remembered `.filelock-*` directory path without confirming that it is still the directory it created. A different local account able to rename entries in a non-sticky shared database directory can substitute a victim-owned directory at that path, causing the lock user's process to delete its contents during cleanup. This route applies to macOS and POSIX setups without a usable /proc/self/fd; stock Linux with /proc mounted is not affected. The advisory also documents a dead-owner sweep variant under specified conditions.
Product: filelock (Python ReadWriteLock and AsyncReadWriteLock). AI system: Anthropic OSS Scanner (model not specified for this finding). Team / organization: Anthropic and filelock maintainers.
CVE identifiers: CVE-2026-112937.
AI and human contribution (source account): The primary filelock advisory explicitly maps the Anthropic OSS Scanner report ANT-2026-LSSZIUEO to this finding. The advisory includes the scanner reproducer and records maintainer review. Anthropic's program sources establish model-based scanning; no model is identified for this item.
Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.
Discovery context: The advisory establishes a publicly disclosed, AI-scanner-reported issue. It is conditional on another local account's rename permissions and affected filesystem route; stock Linux with /proc mounted is excluded. No exploitation or zero-day status is asserted.
Remediation status: fix documented. Fixed in filelock 4.2.1. The advisory discusses hard-link cleanup and stale-link sweep behavior; deployment status is not checked.
A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.
Disclosed 17 Oct 2026. AI attribution dated 17 Oct 2026. Sources checked 14 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 6.1. Documented technical effects: data modification.
Severity, consequences and exploitation evidence
Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.
- CVE-2026-112937: 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. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-112937: data modification.
Prerequisites / affected scope: In a non-sticky parent where another local user has rename access, an attacker can exploit cleanup naming to rename a sibling directory over the private hard-link directory for deletion; deletion is limited by the victim process permissions..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Fixed in filelock 4.2.1. The advisory discusses hard-link cleanup and stale-link sweep behavior; deployment status is not checked.