{
  "id": "cve-2026-112912",
  "title": "SoftFileLock symlink swapping can disclose whether a private path exists or is writable",
  "product": "filelock Python locking library",
  "ai_system": "Anthropic OSS Scanner (model unspecified)",
  "organization": "Anthropic and project maintainers",
  "summary": "During SoftFileLock acquire, the writability check first uses lstat and then os.access, which follows symlinks. A local user able to change entries in the lock directory can swap a marker for a symlink between these calls. The different acquire outcomes reveal one bit indicating whether a chosen path exists or is writable by the lock user; the lock does not open, create, or modify the target through the symlink. Linux fs.protected_symlinks blocks the leak in a sticky world-writable directory such as /tmp, but not in a writable non-sticky or sticky group-writable directory.",
  "ai_role": "The primary filelock advisory says Anthropic OSS Scanner reported this privately as ANT-2026-RQ91AXTW, includes the reproducer and maintainer review, and assigns CVE-2026-112912. The advisory was publicly published Oct 17; Anthropic’s scanner page establishes model-based scanner provenance. No model is specified.",
  "disclosure_date": "2026-10-17",
  "ai_attribution_date": "2026-10-17",
  "classification": "disclosure",
  "classification_note": "The primary maintainer published GHSA-9j6q-wvj5-jgjg on 2026-10-17 and directly credits Anthropic OSS Scanner (ANT-2026-RQ91AXTW). For filelock, the source records private scanner report receipt on Oct 15; the public advisory attribution date remains Oct 17.",
  "cves": [
    "CVE-2026-112912"
  ],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-9j6q-wvj5-jgjg",
  "ai_source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-9j6q-wvj5-jgjg",
  "remediation": "fix documented",
  "remediation_note": "Use a lock directory writable only by the lock account, or a Linux sticky world-writable directory with fs.protected_symlinks enabled. Do not use soft locks as root in directories other accounts can write. filelock 4.2.1 fixes the issue.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-9j6q-wvj5-jgjg",
  "checked_date": "2026-11-14",
  "cvss": [
    {
      "cve": "CVE-2026-112912",
      "version": "3.1",
      "score": 2.5,
      "vector": "CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N",
      "source_url": "https://raw.githubusercontent.com/CVEProject/cvelistV5/main/cves/2026/112xxx/CVE-2026-112912.json",
      "source_name": "GitHub_M (CNA; CVE Program record)",
      "checked_date": "2026-11-16"
    }
  ],
  "impacts": [
    {
      "cves": [
        "CVE-2026-112912"
      ],
      "consequences": [
        "other"
      ],
      "conditions": "filelock is a platform-independent file lock for Python. From 3.32.6 until 4.2.1, SoftFileLock can follow a swapped symbolic link during the conditional os.access writability check for a node without its owner-write bit, allowing another local user on a platform and directory configuration that follows the link to infer whether a chosen path exists and is writable from the observable acquisition result. This issue is fixed in version 4.2.1. CWE-59: Improper Link Resolution Before File Access ('Link Following')",
      "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-112912.json",
      "checked_date": "2026-11-16"
    }
  ]
}
