AI Science Tracker

WindowsFileLock ignores mode and inherits access from its parent directory ACL

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

Finding and attribution

On Windows, filelock does not apply the mode argument as a security descriptor when creating FileLock files or the ReadWriteLock SQLite database. In a directory whose inheritable ACL grants other local accounts access to new files, those accounts can read holder metadata, write lock state where permitted, or take the byte-range lock and make the owner wait or time out. The maintainers independently confirmed this on Windows with two local accounts; Unix is not affected and cooperating-process mutual exclusion remains.

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

CVE identifiers: CVE-2026-112910.

AI and human contribution (source account): The primary filelock advisory explicitly credits Anthropic OSS Scanner with finding ANT-2026-0KEO0DDO, records that maintainers confirmed the Windows behavior with two local accounts, and assigns CVE-2026-112910. The public advisory appeared 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-8mx5-7m5m-r77g on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-0KEO0DDO). 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 Windows file creation. On Windows, store lock files and databases in a directory whose ACL already excludes other accounts, or set explicit ACLs after creation; do not rely on mode=0o600.

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-112910: data disclosure.
Prerequisites / affected scope: On Windows, another local account with inherited directory ACL access can read lock-holder metadata or the ReadWriteLock SQLite database despite mode=0600..
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 Windows file creation. On Windows, store lock files and databases in a directory whose ACL already excludes other accounts, or set explicit ACLs after creation; do not rely on mode=0o600.

Original evidence

Download this source record (JSON)

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