Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
filelock versions 3.30.0 through 4.2.0 are vulnerable in StrictSoftFileLock and AsyncStrictSoftFileLock, which can follow a symbolic link placed in the lock's coordination directory. A local user with an account who can rename that directory, which depends on the directory's permissions, can make the lock create claim files in a directory they choose, and this can block other processes from taking the lock. Upgrade to filelock 4.2.1, the fixed version. The source text is cut off in places.
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 |
|---|---|---|---|---|
| 5.8 | Medium | 3.1 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H | 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:51 UTC Confirmed by the CVE List
- 5 Nov 2026, 22:17 UTC Confirmed by NVD
Sources
- GitHub Advisory Database: GHSA-m462-7rxw-wvpg
- OSV: GHSA-m462-7rxw-wvpg
- github.com/tox-dev/filelock/security/advisories/GHSA-m462-7rxw-wvpg
- github.com/tox-dev/filelock/pull/839
- github.com/tox-dev/filelock/commit/bfa066d65a1ba9106f86ee9d027f7588b9c77e03
- github.com/tox-dev/filelock
- github.com/tox-dev/filelock/releases/tag/4.2.1