AI Science Tracker

filelock can adopt a lock protocol directory created by another user

filelock Python locking library · AI involvement attributed to Anthropic OSS Scanner (model unspecified)

Finding and attribution

StrictSoftFileLock and SoftReadWriteLock accept an existing protocol directory after checking only that it is a directory, not who owns it. Another local user who creates the derived directory before the lock user’s first acquire can remove claims, admit concurrent holders, redirect lock-user writes, or hold acquire/release beyond its timeout. The advisory identifies the pre-creation condition and affected versions.

Product: filelock Python locking library. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and filelock maintainers.

CVE identifiers: CVE-2026-112911.

AI and human contribution (source account): The primary filelock advisory states Anthropic OSS Scanner reported ANT-2026-Q5VK5JEE and logs that four other scanner IDs were moved to separate advisories, so this row maps to one individually described issue. The advisory says maintainers reviewed it. Anthropic’s primary scanner page establishes model-based scanning; the 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 maintainers published GHSA-9c4x-gm8v-wgc4 on Oct 17, 2026 and explicitly credit Anthropic OSS Scanner (ANT-2026-Q5VK5JEE). Their event history records the private scanner report as received Oct 15; that internal report date is not used as the public disclosure or attribution date.

Remediation status: fix documented. Keep lock protocol directories in a location other accounts cannot write. Where a shared directory is necessary, pre-create and verify the protocol tree as the service user. filelock 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 6.3. Documented technical effects: 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-112911: other.
Prerequisites / affected scope: In a shared parent directory, another local user can create/adopt the protocol directory first and alter protocol state so concurrent holders are admitted; this violates the lock protocol. No further impact is established..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.

Documented fix: Keep lock protocol directories in a location other accounts cannot write. Where a shared directory is necessary, pre-create and verify the protocol tree as the service user. filelock 4.2.1 fixes the issue.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases