MediumVulnerabilityCVE-2026-112938updated 28 Oct 2026, 21:08 UTC
filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory…
Fixed in filelock 4.2.1Official source
| Severity | MediumCVSS 5.8 of 10 |
|---|---|
| Being exploited? | UnclearNo reports either way yet |
| Fix available? | Yesfilelock 4.2.1 · since 28 Oct 2026 |
| How sure is this? | Official sourceBacked by an official source |
Are you affected?
| Package / product | Affected versions | Fixed in |
|---|---|---|
| filelock · pip | >= 3.30.0, <= 4.2.0 | 4.2.1 |
Timeline
- 28 Oct 2026, 21:08 UTCPublicly disclosed
- 28 Oct 2026, 21:08 UTCReported by GitHub Advisory · GitHub Advisory
- 28 Oct 2026, 21:08 UTCPicked up by Zero Radar
Sources 1 report, oldest first
Official vendor, government CERT or advisory database
- filelock: StrictSoftFileLock follows a symbolic link swapped in at <path>.filelock and creates claim files in a directory another local user choosesGitHub Advisory · 28 Oct 2026, 21:08 UTC
Technical details
- ID
- CVE-2026-112938 · GHSA-m462-7rxw-wvpg
- CVSS
- 5.8 / 10
- Disclosed
- 28 Oct 2026, 21:08 UTC
- On Zero Radar
- 28 Oct 2026, 21:08 UTC (0 min after disclosure)
- Last change
- 28 Oct 2026, 21:08 UTC
This entry has not been explained yet. The text comes straight from the source. How Zero Radar works