Skip to main content
CVE-2026-112938VulnerabilityPublished Updated

Python filelock: From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate

Affects python-filelockSource GCVE Database

0
Compare
Authoritative record:CVE-2026-112938· Medium 5.8

Not known to be exploited · CVSS 5.8 Medium · fixed in 4.2.1 : update python-filelock when convenient.

Data as of 18 Nov 2026, 15:20 UTC

CVSS 3.1 base score
5.8Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.15.8
Patch
Available – fixed in 4.2.1
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10python-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=stonkingOther threatsAffected
  • 3.20.3-1 – 3.32.2-1
4 affected builds
Fixed in–
Ubuntu 26.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=resoluteOther threatsAffected
  • 3.18.0-1 – 3.20.3-1
4 affected builds
Fixed in–
Ubuntu Pro 24.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/nobleOther threatsAffected
  • 3.12.2-1 – 3.13.1-1ubuntu0.1~esm1
4 affected builds
Fixed in–
Ubuntu Pro 22.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/jammyOther threatsAffected
  • 3.0.12-2 – 3.6.0-1ubuntu0.1~esm1
7 affected builds
Fixed in–
Ubuntu Pro 20.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/focalOther threatsAffected
  • =3.0.12-1
  • =3.0.12-2
  • =3.0.12-2ubuntu0.1~esm1
Fixed in–
Ubuntu Pro 18.04 LTSpython-filelockpkg:deb/ubuntu/python-filelock?arch=source&distro=esm-apps/bionicOther threatsAffected
  • 2.0.11-1 – 3.0.4-1ubuntu0.1~esm1
7 affected builds
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

filelock is a platform-independent file lock for Python. From 3.30.0 until 4.2.1, On POSIX platforms, StrictSoftFileLock and AsyncStrictSoftFileLock validate the coordination directory in _ensure_protocol_directory but later reach the claims directory through _open_directory by pathname, allowing a local account that can rename the coordination name to swap in a symbolic link between check and use during acquisition. That race can create and leave claim files in another writable directory or strand claims in a different strict lock so the second lock times out. Separately, the claims property and force_break follow a resting symbolic link without a race when the lock user inspects or recovers the lock. Claims inspection discloses a file name to the other account only if the resulting exception text or claim_name reaches that account through a shared log, CI output, or error report. A blind force_break recovery that removes live claims from another strict lock can allow two processes into that lock's critical section; this path reaches other strict locks, not arbitrary files. This issue is fixed in version 4.2.1.

References

Community reviews

Loading reviews…