Advisory record · GHSA-567q-5qvw-pf92

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

CVSS 2.5 Low

Published by the GitHub Advisory Database at 23 Oct 2026, 22:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
filelockPyPI>=3.22.0, <4.2.14.2.1
Identifiers
GHSA-567q-5qvw-pf92 · CVE-2026-112907
Weakness (CWE)
CWE-667
Published
23 Oct 2026
Updated
23 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

filelock versions 3.22.0 through 4.2.0 on Windows let a local account that can read a soft lock's marker file hold an oplock on it while no process holds the lock. This makes acquire() wait past its timeout, and stale markers are not broken. Mutual exclusion holds. Upgrade to filelock 4.2.1.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
2.5 Low 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS No score.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV
  3. 5 Nov 2026, 21:50 UTC Confirmed by the CVE List
  4. 5 Nov 2026, 22:17 UTC Confirmed by NVD

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.