{
  "id": "cve-2026-112914",
  "title": "SoftFileLock stale-break restore can follow a swapped symlink and link a private file into the lock directory",
  "product": "filelock Python locking library",
  "ai_system": "Anthropic OSS Scanner (model unspecified)",
  "organization": "Anthropic and project maintainers",
  "summary": "During stale-lock recovery, a local user can race a path check and replace the marker path with a symlink; the restore step then follows it and can create a hard link to a file belonging to the lock user inside the lock directory. The attacker can read metadata and retain a name for the file, and a subsequent FileLock open can truncate or change permissions on the linked file. The advisory limits the affected behavior to specific race conditions, platforms and filelock versions; a sticky directory on tested settings is not affected.",
  "ai_role": "The primary filelock advisory directly credits Anthropic OSS Scanner and maps finding ANT-2026-SB29HIAL to this distinct stale-break restore issue. It includes the relevant source behavior and records maintainer review. 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-crv4-6mhj-j5jh on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-SB29HIAL). For filelock, the source records private scanner report receipt on Oct 15; the public advisory attribution date remains Oct 17.",
  "cves": [
    "CVE-2026-112914"
  ],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh",
  "ai_source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh",
  "remediation": "fix documented",
  "remediation_note": "filelock 4.2.1 fixes the stale-break restore path. Keep soft locks out of directories other local users can write without the sticky bit, and do not take a native FileLock on a path another user controls.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-crv4-6mhj-j5jh",
  "checked_date": "2026-11-14",
  "cvss": [
    {
      "cve": "CVE-2026-112914",
      "version": "3.1",
      "score": 5.3,
      "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112914.json",
      "source_name": "GitHub_M (CNA; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-112914"
      ],
      "consequences": [
        "data disclosure"
      ],
      "conditions": "On a runtime following the swapped symlink, local attacker with rename access in a non-sticky lock directory can cause the lock user to hard-link a private file into that directory.",
      "exploitation": "The cited source does not establish exploitation in the wild.",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112914.json",
      "checked_date": "2026-11-16"
    }
  ]
}
