Finding and attribution
SQLite reopens the lock database by name and processes adjacent journal, WAL and shared-memory side files. Another local account able to create or rename entries in the database directory can make the lock user’s ordinary lock operation write attacker-chosen bytes to the lock user’s files, create or unlink files, admit conflicting readers/writers, or kill a holder. The advisory narrows affected versions and describes how sticky directories reduce but do not remove all denial-of-service variants.
Product: filelock Python locking library. AI system: Anthropic OSS Scanner (model unspecified). Team / organization: Anthropic and filelock maintainers.
CVE identifiers: CVE-2026-112940.
AI and human contribution (source account): The primary filelock advisory explicitly credits Anthropic OSS Scanner with ANT-2026-KMJ2575J and gives the per-finding issue description. It records the scanner report date and maintainers’ review. Anthropic’s primary scanner page establishes model-based scanning; no model is identified for this case.
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-v4x8-3wr5-3wq8 on Oct 17, 2026 and explicitly credit Anthropic OSS Scanner (ANT-2026-KMJ2575J). 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 in a directory only the locking account or root can write, 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: High · highest recorded score 7.1. 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.
- CVE-2026-112940: CVSS 3.1 · 7.1 (High) ·
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H. GitHub_M (CNA; CVE Program record) · checked 16 Nov 2026.
CVE-2026-112940: data modification.
Prerequisites / affected scope: On POSIX, attacker needs rename access in a non-sticky parent to swap database/side-file names. Attacker-chosen content overwrite additionally requires a writable adjacent hot journal; the description also states overwrite or unlink operations..
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 in a directory only the locking account or root can write, and do not share a writable database across accounts. Version 4.2.1 fixes the issue.