CVE-2026-112934
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…
Does this matter?
Lower severity and a low EPSS score (0.23%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 6.1 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
- EPSS
- 0.23% probability · 14th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-62
- Affected
- tox-dev/filelock
- Source
- security-advisories@github.com
EPSS moved from 0.1% on 21 October 2026 to 0.2% on 26 October 2026.
References
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03Patch
- https://github.com/tox-dev/filelock/pull/842Patch
- https://github.com/tox-dev/filelock/releases/tag/4.2.1Release Notes
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845Exploit, Mitigation, Vendor Advisory
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845Exploit, Mitigation, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.