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

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

- **Identifiers:** `GHSA-567q-5qvw-pf92` · `CVE-2026-112907`
- **State:** Confirmed
- **Severity:** CVSS 2.5 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-667](https://cwe.mitre.org/data/definitions/667.html)
- **Tags:** [CWE-667](https://agentprime.io/advisories/tag/cwe-667.md)
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Reviewed by a person:** No

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.

## Affected packages

- `filelock` (PyPI): affected `>=3.22.0, <4.2.1`; fixed in `4.2.1`

## 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

- 2.5 Low, CVSS 3.1: `CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:L`, from 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](https://osv.dev/vulnerability/GHSA-567q-5qvw-pf92)
- 5 Nov 2026, 21:50 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-112907)
- 5 Nov 2026, 22:17 UTC: [Confirmed by NVD](https://nvd.nist.gov/vuln/detail/CVE-2026-112907)

## Sources

- [GitHub Advisory Database: GHSA-567q-5qvw-pf92](https://github.com/advisories/GHSA-567q-5qvw-pf92)
- [OSV: GHSA-567q-5qvw-pf92](https://osv.dev/vulnerability/GHSA-567q-5qvw-pf92)
- <https://github.com/tox-dev/filelock/security/advisories/GHSA-567q-5qvw-pf92>
- <https://github.com/tox-dev/filelock/pull/835>
- <https://github.com/tox-dev/filelock/commit/e1e825b1992f69fb6b346dc395d5ae4893536c0a>
- <https://github.com/tox-dev/filelock>
- <https://github.com/tox-dev/filelock/releases/tag/4.2.1>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-567q-5qvw-pf92>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-567q-5qvw-pf92/>. Everything for agents: <https://agentprime.io/llms.txt>.