AI Science Tracker

SoftReadWriteLock can write through a replaced holder record and block lock operations

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

Finding and attribution

SoftReadWriteLock refreshes holder records by reopening a path and writing without checking the opened file type. A different local user who owns or can write the lock’s .rw tree can replace a record with a FIFO, making waiting acquires hang beyond timeout and blocking a holder heartbeat so a second process can enter while the first still believes it holds the lock. Where the OS permits cross-owner hard links, it can also make the lock user overwrite the first roughly 135 bytes of one of its own private files with the holder record. The FIFO issue works on default Linux; the hard-link variant has additional OS policy requirements.

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

CVE identifiers: CVE-2026-112934.

AI and human contribution (source account): The primary filelock advisory explicitly says Anthropic OSS Scanner reported ANT-2026-AT33VEVC, includes the scanner’s reproducer and maintainer review, and assigns CVE-2026-112934. 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-fj95-fr6c-h845 on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-AT33VEVC). 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 checks and protects holder-record operations. Keep the lock tree in a directory only the locking account can write, and in sticky shared locations ensure the lock account creates and owns the .rw tree first. Keep fs.protected_hardlinks enabled where supported; this mitigates the hard-link variant but not the FIFO stall.

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.1. Documented technical effects: data modification, denial of service, 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-112934: data modification, denial of service, other.
Prerequisites / affected scope: filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1. CWE-62: UNIX Hard Link.
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 checks and protects holder-record operations. Keep the lock tree in a directory only the locking account can write, and in sticky shared locations ensure the lock account creates and owns the .rw tree first. Keep fs.protected_hardlinks enabled where supported; this mitigates the hard-link variant but not the FIFO stall.

Original evidence

Download this source record (JSON)

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