Finding and attribution
A local user who can write but cannot remove a live lock marker can replace its owner record with a nonexistent PID. A contender running as the lock owner then judges the lock stale, removes the live marker, and acquires it; two processes enter the critical section concurrently without an error. This requires group/other write permission on the marker, such as explicit mode=0o666 or a lax umask, and a contender of the holder account. Default mode under umask 022 is not affected.
Product: filelock SoftFileLock, MarkerSoftFileLock, SoftFileLease, async variants, and FileLock soft-lock fallback. AI system: Anthropic OSS Scanner. Team / organization: Anthropic.
CVE identifiers: CVE-2026-112939.
AI and human contribution (source account): The maintainer advisory says reported by Anthropic’s OSS Scanner (automated analysis), ANT-2026-W1H9NXUH, received 2026-10-15; maintainers reviewed it.
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 advisory documents the flaw and patch; it does not report observed exploitation.
Remediation status: fix documented. Fixed in filelock 4.2.1 (PR #836). Avoid group/other write bits on soft markers, lax umasks in shared directories, and shared writable lock directories.
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 16 Nov 2026; these are separate dates, not a live installation check.
Recorded CVSS: Medium · highest recorded score 4.7. 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-112939: CVSS 3.1 · 4.7 (Medium) ·
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:N. filelock maintainer advisory · checked 16 Nov 2026.
CVE-2026-112939: other.
Prerequisites / affected scope: Source records a local cross-account lock-integrity failure under the version and filesystem or permission conditions stated in the summary..
Exploitation evidence: No observed exploitation is reported.. Impact source · checked 16 Nov 2026.
Documented fix: Fixed in filelock 4.2.1 (PR #836). Avoid group/other write bits on soft markers, lax umasks in shared directories, and shared writable lock directories.