AI Science Tracker

SoftFileLock stale-break restore can follow a swapped symlink and link a private file into the lock directory

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

Finding and attribution

During stale-lock recovery, a local user can race a path check and replace the marker path with a symlink; the restore step then follows it and can create a hard link to a file belonging to the lock user inside the lock directory. The attacker can read metadata and retain a name for the file, and a subsequent FileLock open can truncate or change permissions on the linked file. The advisory limits the affected behavior to specific race conditions, platforms and filelock versions; a sticky directory on tested settings is not affected.

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

CVE identifiers: CVE-2026-112914.

AI and human contribution (source account): The primary filelock advisory directly credits Anthropic OSS Scanner and maps finding ANT-2026-SB29HIAL to this distinct stale-break restore issue. It includes the relevant source behavior and records maintainer review. The advisory was published Oct 17; Anthropic’s scanner page establishes model-based scanner provenance.

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 primary maintainer published GHSA-crv4-6mhj-j5jh on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-SB29HIAL). For filelock, the source records private scanner report receipt on Oct 15; the public advisory attribution date remains Oct 17.

Remediation status: fix documented. filelock 4.2.1 fixes the stale-break restore path. Keep soft locks out of directories other local users can write without the sticky bit, and do not take a native FileLock on a path another user controls.

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: data disclosure.

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-112914: data disclosure.
Prerequisites / affected scope: On a runtime following the swapped symlink, local attacker with rename access in a non-sticky lock directory can cause the lock user to hard-link a private file into that directory..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: filelock 4.2.1 fixes the stale-break restore path. Keep soft locks out of directories other local users can write without the sticky bit, and do not take a native FileLock on a path another user controls.

Original evidence

Download this source record (JSON)

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