{
  "id": "cve-2026-112937",
  "title": "filelock ReadWriteLock cleanup can recursively delete a directory substituted at its hard-link path",
  "product": "filelock (Python ReadWriteLock and AsyncReadWriteLock)",
  "ai_system": "Anthropic OSS Scanner (model not specified for this finding)",
  "organization": "Anthropic and filelock maintainers",
  "summary": "On the private hard-link route, filelock recursively removes a remembered `.filelock-*` directory path without confirming that it is still the directory it created. A different local account able to rename entries in a non-sticky shared database directory can substitute a victim-owned directory at that path, causing the lock user's process to delete its contents during cleanup. This route applies to macOS and POSIX setups without a usable /proc/self/fd; stock Linux with /proc mounted is not affected. The advisory also documents a dead-owner sweep variant under specified conditions.",
  "ai_role": "The primary filelock advisory explicitly maps the Anthropic OSS Scanner report ANT-2026-LSSZIUEO to this finding. The advisory includes the scanner reproducer and records maintainer review. Anthropic's program sources establish model-based scanning; no model is identified for this item.",
  "disclosure_date": "2026-10-17",
  "ai_attribution_date": "2026-10-17",
  "classification": "disclosure",
  "classification_note": "The advisory establishes a publicly disclosed, AI-scanner-reported issue. It is conditional on another local account's rename permissions and affected filesystem route; stock Linux with /proc mounted is excluded. No exploitation or zero-day status is asserted.",
  "cves": [
    "CVE-2026-112937"
  ],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85",
  "ai_source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85",
  "remediation": "fix documented",
  "remediation_note": "Fixed in filelock 4.2.1. The advisory discusses hard-link cleanup and stale-link sweep behavior; deployment status is not checked.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-jqc4-5cvw-7w85",
  "checked_date": "2026-11-14",
  "cvss": [
    {
      "cve": "CVE-2026-112937",
      "version": "3.1",
      "score": 6.1,
      "vector": "CVSS:3.1/AV:L/AC:L/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-112937.json",
      "source_name": "GitHub_M (CNA; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-112937"
      ],
      "consequences": [
        "data modification"
      ],
      "conditions": "In a non-sticky parent where another local user has rename access, an attacker can exploit cleanup naming to rename a sibling directory over the private hard-link directory for deletion; deletion is limited by the victim process permissions.",
      "exploitation": "Exploitation in the wild is not established by the cited description.",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112937.json",
      "checked_date": "2026-11-16"
    }
  ]
}
