CVE-2026-112938

MEDIUM
MEDIUM Priority: 0.01 BB Relevance: 27/100
Published: 2026-11-05 Modified: 2026-11-09 First seen: 2026-11-05 Status: active

Attack Surface

No Interaction

CVSS Vector Breakdown

AV: Local
AC: High
PR: Low
UI: None
S: Unchanged
C: Low
I: Low
A: High

Description

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1.

Affected Software (2)

VendorProductVersion
tox-dev filelock >= 3.30.0, < 4.2.1
tox-dev filelock >= 3.30.0, < 4.2.1

Bug Bounty Relevance

27 / 100
✓ No user interaction

CVSS Score

5.8 / 10.0 v3.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

EPSS — Exploitation Probability

0.11%
Raw Score 0.001070
Percentile 1.2%
Date 2026-11-14

EPSS Trend

2026-11-14
0.00107
2026-11-13
0.00107
2026-11-12
0.00107
2026-11-10
0.00107
2026-11-09
0.00107
2026-11-08
0.00107
2026-11-07
0.00107
2026-11-06
0.00107

Intelligence Sources

mitre ref →
nvd ref →