AI Science Tracker

StrictSoftFileLock claim directories can let another user remove a live hold

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

Finding and attribution

StrictSoftFileLock creates the directories containing claim files with bare mkdir calls, so a permissive umask or default ACL can leave them writable by another local user despite a restrictive lock-file mode. That user can unlink the 0600 claims; a later contender then enters while the original holder believes it still holds the lock. The advisory documents the required permission settings and says the common 022 umask without permissive ACLs does not allow the unlink.

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

CVE identifiers: CVE-2026-112908.

AI and human contribution (source account): The primary filelock advisory explicitly credits Anthropic OSS Scanner (automated analysis) with finding ANT-2026-AD6SUOON, provides a reproducer, records maintainer review, and states that this issue was split from a grouped draft into its own 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-6627-m3xw-93mp on Oct 17, 2026 and directly credits Anthropic OSS Scanner (ANT-2026-AD6SUOON). 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. filelock 4.2.1 fixes the issue. Use restrictive umask, avoid default ACLs that grant other users write access to claim directories, and keep strict locks in directories other accounts cannot write. Existing .filelock trees may need permission correction after upgrade.

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.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-112908: other.
Prerequisites / affected scope: filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1. CWE-732: Incorrect Permission Assignment for Critical Resource.
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: filelock 4.2.1 fixes the issue. Use restrictive umask, avoid default ACLs that grant other users write access to claim directories, and keep strict locks in directories other accounts cannot write. Existing .filelock trees may need permission correction after upgrade.

Original evidence

Download this source record (JSON)

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