CVE-2026-112934
CVE-2026-112934 is a medium-severity vulnerability in Tox-dev Filelock with a CVSS 3.x base score of 6.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-62.
Key facts
- Severity: Medium (CVSS 3.x base score 6.1)
- EPSS exploit prediction: 0% (14th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-62
- Affected product: Tox-dev Filelock
- Published:
- Last modified:
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.
Frequently asked questions
- What is CVE-2026-112934?
- 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.
- How severe is CVE-2026-112934?
- CVE-2026-112934 has a CVSS 3.x base score of 6.1, rated medium severity. It is exploitable over local access with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
- Is CVE-2026-112934 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (14th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2026-112934?
- CVE-2026-112934 affects Tox-dev Filelock. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2026-112934?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- When was CVE-2026-112934 published?
- CVE-2026-112934 was published on 2026-10-20 and last updated on 2026-10-22.
References
- https://github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- https://github.com/tox-dev/filelock/pull/842
- https://github.com/tox-dev/filelock/releases/tag/4.2.1
- https://github.com/tox-dev/filelock/security/advisories/GHSA-fj95-fr6c-h845
Affected products (1)
- cpe:2.3:a:tox-dev:filelock:*:*:*:*:*:python:*:*
More vulnerabilities in Tox-dev Filelock
- CVE-2026-112940 — High (CVSS 7.1): filelock is a platform-independent file lock for Python. From 3.20.4 until 4.2.1, ReadWriteLock let SQLite reopen the…
- CVE-2026-112911 — Medium (CVSS 6.3): filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, StrictSoftFileLock versions from…
- CVE-2025-68146 — Medium (CVSS 6.3): filelock is a platform-independent file lock for Python. In versions prior to 3.20.1, a Time-of-Check-Time-of-Use…
- CVE-2026-112937 — Medium (CVSS 6.1): filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, ReadWriteLock can remove a randomized…
- CVE-2026-112936 — Medium (CVSS 6.1): filelock is a platform-independent file lock for Python. From 3.20.4 until 4.0.9, ReadWriteLock and AsyncReadWriteLock…
- CVE-2026-112909 — Medium (CVSS 6.1): filelock is a platform-independent file lock for Python. Prior to 4.2.1, UnixFileLock can truncate a regular file…
All CVEs affecting Tox-dev Filelock →
Other CWE-62 vulnerabilities
- CVE-2026-109518 — High (CVSS 7.7): On Debian, Ubuntu, and derivative Linux distributions, an on-path attacker who can manipulate the HTTP traffic…