{
  "id": "ghsa-wfhq-q4j2-c37m",
  "title": "filelock SoftReadWriteLock can follow a substituted lock tree and write outside its directory",
  "product": "filelock Python SoftReadWriteLock and AsyncSoftReadWriteLock",
  "ai_system": "Anthropic OSS Scanner; exact model/version not identified for this finding",
  "organization": "Anthropic and tox-dev/filelock maintainers",
  "summary": "After a lock object validates its .rw tree once, another local account with write access to the parent can replace a nested gen or holders directory with a symlink. Later lock operations then create, replace, or delete the lock user’s own protocol files under another path, including a private Git repository. The advisory demonstrates replacement of .git/HEAD causing git status to fail. This requires a long-lived lock object and a writable shared parent; in a sticky directory such as /tmp, the attacker must plant the lock tree before the victim first acquires it. The documented reproducer ran on Linux; equivalent path behavior is described for POSIX and Windows junctions.",
  "ai_role": "The primary filelock advisory explicitly says Anthropic’s OSS Scanner reported this exact finding as ANT-2026-WXXRI4M4, includes the scanner reproducer, and notes maintainer review. Anthropic’s official OSS Scanner description says enrolled repositories receive periodic security scans by its strongest models. The specific model is not named.",
  "disclosure_date": "2026-10-17",
  "ai_attribution_date": "2026-10-17",
  "classification": "disclosure",
  "classification_note": "The public advisory rates the issue Low (CVSS 3.3) and classifies it as conditional security. A different local account needs write access to the lock parent; a long-lived lock object must perform multiple acquisitions. The scanner had reported it privately on Oct 15; the public attribution is dated to the advisory publication Oct 17.",
  "cves": [],
  "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m",
  "ai_source_url": "https://red.anthropic.com/oss-scanner/",
  "remediation": "fix documented",
  "remediation_note": "Fixed in filelock 4.2.1. The advisory recommends protecting every ancestor of the lock path from replacement by another account; a sticky shared parent can suffice if the lock tree was not planted beforehand. Deployment status is not checked.",
  "advisory_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m",
  "checked_date": "2026-11-14",
  "impacts": [
    {
      "cves": [],
      "consequences": [
        "data modification"
      ],
      "conditions": "The filelock advisory title states substituted lock tree can make SoftReadWriteLock write outside its intended directory; exact modified object/prerequisite needs full advisory review.",
      "exploitation": "The cited source does not establish exploitation in the wild.",
      "source_url": "https://github.com/tox-dev/filelock/security/advisories/GHSA-wfhq-q4j2-c37m",
      "checked_date": "2026-11-16"
    }
  ]
}
