Finding and attribution
StrictSoftFileLock checks the coordination directory with lstat, then later uses the path by name. Another local user able to rename the directory can exchange it for a symlink between those operations, causing the lock-user process to create claim files in a directory the attacker chooses. This can strand claims that deny another strict lock or make multiple holders enter a critical section. The advisory limits the issue to POSIX-style conditions and lists the relevant shared-directory and pre-created-link cases.
Product: filelock Python locking library. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and filelock maintainers.
CVE identifiers: CVE-2026-112938.
AI and human contribution (source account): The primary filelock advisory explicitly credits Anthropic OSS Scanner (automated analysis) with finding ANT-2026-SVFEYX89, provides a scanner reproducer, records maintainer review, and states this was split from the grouped advisory. The report was received Oct 15; the public advisory was published Oct 17. Anthropic’s scanner page establishes AI-model provenance; exact model is unspecified.
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 filelock maintainer published GHSA-m462-7rxw-wvpg on Oct 17, 2026 and directly credits Anthropic OSS Scanner (ANT-2026-SVFEYX89). The internal scanner report was received Oct 15; that report date is retained in evidence and is not used as public attribution date.
Remediation status: fix documented. Keep strict locks in directories other users cannot write. In sticky shared directories, create and verify the lock directory as the service account before other users can claim it. Version 4.2.1 fixes the issue.
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 5.8. Documented technical effects: denial of service, other.
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-112938: CVSS 3.1 · 5.8 (Medium) ·
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-112938: denial of service, other.
Prerequisites / affected scope: filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1. CWE-363: Race Condition Enabling Link Following.
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Keep strict locks in directories other users cannot write. In sticky shared directories, create and verify the lock directory as the service account before other users can claim it. Version 4.2.1 fixes the issue.