{
  "id": "cve-2026-112934",
  "title": "SoftReadWriteLock can write through a replaced holder record and block lock operations",
  "product": "filelock Python locking library",
  "ai_system": "Anthropic OSS Scanner (model unspecified)",
  "organization": "Anthropic and project maintainers",
  "summary": "SoftReadWriteLock refreshes holder records by reopening a path and writing without checking the opened file type. A different local user who owns or can write the lock’s .rw tree can replace a record with a FIFO, making waiting acquires hang beyond timeout and blocking a holder heartbeat so a second process can enter while the first still believes it holds the lock. Where the OS permits cross-owner hard links, it can also make the lock user overwrite the first roughly 135 bytes of one of its own private files with the holder record. The FIFO issue works on default Linux; the hard-link variant has additional OS policy requirements.",
  "ai_role": "The primary filelock advisory explicitly says Anthropic OSS Scanner reported ANT-2026-AT33VEVC, includes the scanner’s reproducer and maintainer review, and assigns CVE-2026-112934. The advisory was published Oct 17; Anthropic’s scanner page establishes model-based scanner provenance.",
  "disclosure_date": "2026-10-17",
  "ai_attribution_date": "2026-10-17",
  "classification": "disclosure",
  "classification_note": "The primary maintainer published GHSA-fj95-fr6c-h845 on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-AT33VEVC). For filelock, the source records private scanner report receipt on Oct 15; the public advisory attribution date remains Oct 17.",
  "cves": [
    "CVE-2026-112934"
  ],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845",
  "ai_source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845",
  "remediation": "fix documented",
  "remediation_note": "filelock 4.2.1 checks and protects holder-record operations. Keep the lock tree in a directory only the locking account can write, and in sticky shared locations ensure the lock account creates and owns the .rw tree first. Keep fs.protected_hardlinks enabled where supported; this mitigates the hard-link variant but not the FIFO stall.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845",
  "checked_date": "2026-11-14",
  "cvss": [
    {
      "cve": "CVE-2026-112934",
      "version": "3.1",
      "score": 6.1,
      "vector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112934.json",
      "source_name": "GitHub_M (CNA; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-112934"
      ],
      "consequences": [
        "data modification",
        "denial of service",
        "other"
      ],
      "conditions": "filelock is a platform-independent file lock for Python. From 4.0.0 until 4.2.1, SoftReadWriteLock refreshes holder records by name, allowing another local user with rename access to the lock directory to replace a record with a named pipe and stall the lock, or under a permissive hard-link policy to link a reachable target file and cause the lock user to write through it. This issue is fixed in version 4.2.1. CWE-62: UNIX Hard Link",
      "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-112934.json",
      "checked_date": "2026-11-16"
    }
  ]
}
