The classifier judged this item not relevant to AI security, so it is left out of lists, feeds, the API and dataset releases. If that is wrong, report a correction on this page.
GHSA-wfhq-q4j2-c37m: filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lock
- Identifiers
- CVE-2026-112941GHSA-wfhq-q4j2-c37m
- Published
- Record updated
- Affected
- filelock >= 4.1.0, <= 4.2.0
- Fixed in
- 4.2.1
- Known exploitation
- Not listed in the CISA Known Exploited Vulnerabilities catalog at the last check.
- EPSS
- 0.1%
Summary
filelock versions 4.1.0 through 4.2.0 ship SoftReadWriteLock and AsyncSoftReadWriteLock, which check the `<path>.rw`, `gen` and `holders` directories for symbolic links only once per lock object. A local user who can write the lock's parent directory, or who pre-creates `<path>.rw` in a sticky directory such as `/tmp`, can swap in a tree whose `gen` or `holders` links into the lock user's directories. The lock user's long-running process then creates, renames and deletes files there with its own privileges. Anthropic's OSS Scanner reported it as ANT-2026-WXXRI4M4, and the advisory scores it CVSS 3.3 (Low).
Mitigation
The source does not state a fix yet. Check the original advisory for updates.
Affected packages in the Exposure Registry
Matched by package name and ecosystem. Each entry shows whether the package delegates to a language model and how many tracked packages depend on it.
- filelockPyPINo LLM dependency detected · 42 tracked dependents