AI Science Tracker

SoftFileLock stale-lock breaking can remove a live marker after inode reuse

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

Finding and attribution

The stale-lock breaker closes its marker after checking the inode and timestamp, allowing a filesystem that immediately reuses inode numbers to make a later live marker appear stale. Another local user able to create files in the lock directory can force the race, unlinking the live marker so two processes enter the same protected section without warning. The advisory reports the race on ext4, xfs and overlayfs over them; tmpfs, btrfs, a single contender and StrictSoftFileLock are not affected.

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

CVE identifiers: CVE-2026-112935.

AI and human contribution (source account): The primary filelock advisory says Anthropic OSS Scanner (automated analysis) reported the finding on Oct 15, identifies ANT-2026-KIIS96IX, and says maintainers reviewed it. The public advisory appeared Oct 17. Anthropic’s primary scanner program page establishes model-based scanning; no specific model is identified.

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-fq56-3cx3-fjxp on Oct 17, 2026 and explicitly credit Anthropic OSS Scanner (ANT-2026-KIIS96IX). 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 soft locks in a directory other local users cannot write, use tmpfs, or prefer native FileLock where available; StrictSoftFileLock is unaffected. 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 4.7. 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-112935: other.
Prerequisites / affected scope: Race may remove a live stale-lock successor after inode reuse, admitting two simultaneous lock holders; mutual exclusion failure only..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: Keep soft locks in a directory other local users cannot write, use tmpfs, or prefer native FileLock where available; StrictSoftFileLock is unaffected. 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