filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break

影響: pip:filelock >= 3.22.0, <= 4.2.0 → 4.2.1

On Windows the soft locks (SoftFileLock, MarkerSoftFileLock, SoftFileLease, their async forms, and a FileLock that fell back to a soft lock) read their marker by path. The marker is the lock file whose presence says a process holds the lock. Each acquire() attempt that finds a marker opens it with os.open to read the holder's process id, and the lock renames and deletes a marker it judges stale, by path. On Windows each of these calls waits for an oplock. An oplock (opportunistic lock) is a req…

Read on GitHub Advisory Database

On 10/24/2026, 07:27 AM, GitHub Advisory Database published "filelock: On Windows an oplock on a soft lock's marker holds SoftFileLock.acquire() past its timeout and blocks the stale break" (type: Advisory). Severity is "Low" (low). Related technologies: Python. CVE: CVE-2026-112907.