Finding and attribution
During SoftFileLock acquire, the writability check first uses lstat and then os.access, which follows symlinks. A local user able to change entries in the lock directory can swap a marker for a symlink between these calls. The different acquire outcomes reveal one bit indicating whether a chosen path exists or is writable by the lock user; the lock does not open, create, or modify the target through the symlink. Linux fs.protected_symlinks blocks the leak in a sticky world-writable directory such as /tmp, but not in a writable non-sticky or sticky group-writable directory.
Product: filelock Python locking library. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and project maintainers.
CVE identifiers: CVE-2026-112912.
AI and human contribution (source account): The primary filelock advisory says Anthropic OSS Scanner reported this privately as ANT-2026-RQ91AXTW, includes the reproducer and maintainer review, and assigns CVE-2026-112912. The advisory was publicly published Oct 17; Anthropic’s scanner page establishes model-based scanner provenance. No model is specified.
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-9j6q-wvj5-jgjg on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-RQ91AXTW). For filelock, the source records private scanner report receipt on Oct 15; the public advisory attribution date remains Oct 17.
Remediation status: fix documented. Use a lock directory writable only by the lock account, or a Linux sticky world-writable directory with fs.protected_symlinks enabled. Do not use soft locks as root in directories other accounts can write. 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: Low · highest recorded score 2.5. 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-112912: CVSS 3.1 · 2.5 (Low) ·
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-112912: other.
Prerequisites / affected scope: filelock is a platform-independent file lock for Python. From 3.32.6 until 4.2.1, SoftFileLock can follow a swapped symbolic link during the conditional os.access writability check for a node without its owner-write bit, allowing another local user on a platform and directory configuration that follows the link to infer whether a chosen path exists and is writable from the observable acquisition result. This issue is fixed in version 4.2.1. CWE-59: Improper Link Resolution Before File Access ('Link Following').
Exploitation evidence: The cited source does not state whether this issue was exploited in the wild.. Impact source · checked 16 Nov 2026.
Documented fix: Use a lock directory writable only by the lock account, or a Linux sticky world-writable directory with fs.protected_symlinks enabled. Do not use soft locks as root in directories other accounts can write. filelock 4.2.1 fixes the issue.