AI Science Tracker

filelock SoftReadWriteLock can follow a substituted lock tree and write outside its directory

filelock Python SoftReadWriteLock and AsyncSoftReadWriteLock · AI involvement attributed to Anthropic OSS Scanner; exact model/version not identified for this finding

Finding and attribution

After a lock object validates its .rw tree once, another local account with write access to the parent can replace a nested gen or holders directory with a symlink. Later lock operations then create, replace, or delete the lock user’s own protocol files under another path, including a private Git repository. The advisory demonstrates replacement of .git/HEAD causing git status to fail. This requires a long-lived lock object and a writable shared parent; in a sticky directory such as /tmp, the attacker must plant the lock tree before the victim first acquires it. The documented reproducer ran on Linux; equivalent path behavior is described for POSIX and Windows junctions.

Product: filelock Python SoftReadWriteLock and AsyncSoftReadWriteLock. AI system: Anthropic OSS Scanner; exact model/version not identified for this finding. Team / organization: Anthropic and tox-dev/filelock maintainers.

CVE identifiers: Not established in the cited evidence.

AI and human contribution (source account): The primary filelock advisory explicitly says Anthropic’s OSS Scanner reported this exact finding as ANT-2026-WXXRI4M4, includes the scanner reproducer, and notes maintainer review. Anthropic’s official OSS Scanner description says enrolled repositories receive periodic security scans by its strongest models. The specific model is not named.

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 public advisory rates the issue Low (CVSS 3.3) and classifies it as conditional security. A different local account needs write access to the lock parent; a long-lived lock object must perform multiple acquisitions. The scanner had reported it privately on Oct 15; the public attribution is dated to the advisory publication Oct 17.

Remediation status: fix documented. Fixed in filelock 4.2.1. The advisory recommends protecting every ancestor of the lock path from replacement by another account; a sticky shared parent can suffice if the lock tree was not planted beforehand. Deployment status is not checked.

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: Not available · no assessment established here. Documented technical effects: data modification.

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.

No source-backed CVSS assessment is established in this catalog.

Case-level evidence: data modification.
Prerequisites / affected scope: The filelock advisory title states substituted lock tree can make SoftReadWriteLock write outside its intended directory; exact modified object/prerequisite needs full advisory review..
Exploitation evidence: The cited source does not establish exploitation in the wild.. Impact source · checked 16 Nov 2026.

Documented fix: Fixed in filelock 4.2.1. The advisory recommends protecting every ancestor of the lock path from replacement by another account; a sticky shared parent can suffice if the lock tree was not planted beforehand. Deployment status is not checked.

Original evidence

Download this source record (JSON)

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