{
  "id": "cve-2026-112908",
  "title": "StrictSoftFileLock claim directories can let another user remove a live hold",
  "product": "filelock Python locking library",
  "ai_system": "Anthropic OSS Scanner (model unspecified)",
  "organization": "Anthropic and filelock maintainers",
  "summary": "StrictSoftFileLock creates the directories containing claim files with bare mkdir calls, so a permissive umask or default ACL can leave them writable by another local user despite a restrictive lock-file mode. That user can unlink the 0600 claims; a later contender then enters while the original holder believes it still holds the lock. The advisory documents the required permission settings and says the common 022 umask without permissive ACLs does not allow the unlink.",
  "ai_role": "The primary filelock advisory explicitly credits Anthropic OSS Scanner (automated analysis) with finding ANT-2026-AD6SUOON, provides a reproducer, records maintainer review, and states that this issue was split from a grouped draft into its own advisory. The report was received Oct 15; the public advisory was published Oct 17. Anthropic’s scanner page establishes AI-model provenance; exact model is unspecified.",
  "disclosure_date": "2026-10-17",
  "ai_attribution_date": "2026-10-17",
  "classification": "disclosure",
  "classification_note": "The filelock maintainer published GHSA-6627-m3xw-93mp on Oct 17, 2026 and directly credits Anthropic OSS Scanner (ANT-2026-AD6SUOON). The internal scanner report was received Oct 15; that report date is retained in evidence and is not used as public attribution date.",
  "cves": [
    "CVE-2026-112908"
  ],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-6627-m3xw-93mp",
  "ai_source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-6627-m3xw-93mp",
  "remediation": "fix documented",
  "remediation_note": "filelock 4.2.1 fixes the issue. Use restrictive umask, avoid default ACLs that grant other users write access to claim directories, and keep strict locks in directories other accounts cannot write. Existing .filelock trees may need permission correction after upgrade.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-6627-m3xw-93mp",
  "checked_date": "2026-11-14",
  "cvss": [
    {
      "cve": "CVE-2026-112908",
      "version": "3.1",
      "score": 5.3,
      "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:L",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112908.json",
      "source_name": "GitHub_M (CNA; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-112908"
      ],
      "consequences": [
        "other"
      ],
      "conditions": "filelock is a platform-independent file lock for Python. From version 3.30.0 until version 4.2.1, StrictSoftFileLock and AsyncStrictSoftFileLock on POSIX systems create coordination and claim directories without applying the caller’s restrictive lock mode. A permissive umask or inherited default ACL can leave these directories writable by another local user, allowing that user to delete an active holder’s claims. Another authorized process can then acquire the lock while the original holder remains in its critical section. An attacker can also plant malformed claims to prevent acquisition. This issue is fixed in version 4.2.1. CWE-732: Incorrect Permission Assignment for Critical Resource",
      "exploitation": "The cited source does not state whether this issue was exploited in the wild.",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112908.json",
      "checked_date": "2026-11-16"
    }
  ]
}
