Connect your agent
AdvisoriesCriticalCheck your lockfilePluginHow it worksPricing Connect your agent

Advisory record · GHSA-crv4-6mhj-j5jh

filelock: SoftFileLock stale-break restore follows a swapped-in symbolic link and hard-links a file of the user running the lock into the lock directory

CVSS 5.3 MediumEPSS 0.0016 · 5th percentile

Published by the GitHub Advisory Database at 23 Oct 2026, 22:00 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
filelockPyPI>=4.1.0, <4.2.14.2.1
Identifiers
GHSA-crv4-6mhj-j5jh · CVE-2026-112914
Weakness (CWE)
CWE-59 · CWE-363
Tags
Published
23 Oct 2026
Updated
23 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions 4.1.0 through 4.2.0 of the filelock Python package (PyPI) are affected, and version 4.2.1 fixes this. In the soft-lock stale-break restore path, a local user who can write a shared lock directory without the sticky bit can swap in a symbolic link so that the lock user's process hard-links one of its own files into that directory. The other user can then read the file's size, times, mode and owner, and can rename the new name; on 4.2.0 a later lock truncated the file. Upgrade to filelock 4.2.1 or later.

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

ScoreRatingCVSSVectorSource
5.3 Medium 3.1 CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0016, the 5th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

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.