LowVulnerabilityCVE-2026-112941updated 28 Oct 2026, 21:09 UTC
filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of…
Fixed in filelock 4.2.1Official source
| Severity | LowCVSS 3.3 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 | >= 4.1.0, <= 4.2.0 | 4.2.1 |
Timeline
- 28 Oct 2026, 21:09 UTCPublicly disclosed
- 28 Oct 2026, 21:09 UTCReported by GitHub Advisory · GitHub Advisory
- 28 Oct 2026, 21:09 UTCPicked up by Zero Radar
Sources 1 report, oldest first
Official vendor, government CERT or advisory database
- filelock: SoftReadWriteLock follows a lock tree swapped in after its first acquire and writes lock records into directories of the user running the lockGitHub Advisory · 28 Oct 2026, 21:09 UTC
Technical details
- ID
- CVE-2026-112941 · GHSA-wfhq-q4j2-c37m
- CVSS
- 3.3 / 10
- EPSS
- 0.1% chance of exploitation within 30 days
- Disclosed
- 28 Oct 2026, 21:09 UTC
- On Zero Radar
- 28 Oct 2026, 21:09 UTC (1 min after disclosure)
- Last change
- 28 Oct 2026, 21:09 UTC
This entry has not been explained yet. The text comes straight from the source. How Zero Radar works