Finding and attribution
SQLite loads the full schema at each ReadWriteLock acquire, while the timeout only bounds lock waits. Another local account able to place or replace the database file can provide a small crafted schema that stalls acquires while allocating about 1 GB, or makes them loop at full CPU indefinitely. The effect is availability only; the advisory specifies the writable/replacable database-path precondition and affected filelock versions.
Product: filelock Python locking library. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and filelock maintainers.
CVE identifiers: CVE-2026-112915.
AI and human contribution (source account): The primary filelock advisory explicitly says Anthropic OSS Scanner reported ANT-2026-NFPRHMYJ, gives the finding title and severity, and records maintainers’ review. Its event history says it was split from a group draft into an individual issue. Anthropic’s primary scanner page establishes model-based scanning; the model is unspecified.
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 filelock maintainers published GHSA-cwqr-hh33-gh44 on Oct 17, 2026 and explicitly credit Anthropic OSS Scanner (ANT-2026-NFPRHMYJ). Their event history records the private scanner report as received Oct 15; that internal report date is not used as the public disclosure or attribution date.
Remediation status: fix documented. Keep the lock database and its parent directories writable only by the locking account, and do not share a writable database across accounts. Version 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: Medium · highest recorded score 5.5. Documented technical effects: denial of service.
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-112915: CVSS 3.1 · 5.5 (Medium) ·
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-112915: denial of service.
Prerequisites / affected scope: A local user able to replace the SQLite lock database can supply a crafted schema that makes ReadWriteLock acquisition stall or hang; initial/per-acquisition exposure varies by affected version..
Exploitation evidence: Exploitation in the wild is not established by the cited description.. Impact source · checked 16 Nov 2026.
Documented fix: Keep the lock database and its parent directories writable only by the locking account, and do not share a writable database across accounts. Version 4.2.1 fixes the issue.