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.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 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
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
- 5 Nov 2026, 21:50 UTC Confirmed by the CVE List
- 5 Nov 2026, 22:17 UTC Confirmed by NVD
Sources
- GitHub Advisory Database: GHSA-567q-5qvw-pf92
- OSV: GHSA-567q-5qvw-pf92
- github.com/tox-dev/filelock/security/advisories/GHSA-567q-5qvw-pf92
- github.com/tox-dev/filelock/pull/835
- github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a
- github.com/tox-dev/filelock
- github.com/tox-dev/filelock/releases/tag/4.2.1