Use of Multiple Resources with Duplicate Identifier Affecting python-filelock package, versions *


Severity

Recommended
low

Based on default assessment until relevant scores are available.

Threat Intelligence

EPSS
0.21% (10th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-ECHOLATEST-PYTHONFILELOCK-21368019
  • published21 Oct 2026
  • disclosed20 Oct 2026

Introduced: 20 Oct 2026

NewCVE-2026-112906  (opens in a new tab)
CWE-694  (opens in a new tab)

How to fix?

There is no fixed version for Echo:latest python-filelock.

NVD Description

Note: Versions mentioned in the description apply only to the upstream python-filelock package and not the python-filelock package as distributed by Echo. See How to fix? for Echo:latest relevant fixed versions and status.

filelock is a platform-independent file lock for Python. From 4.1.0 until 4.2.1, SoftFileLock versions from 4.1.0 can reuse a stale observation when an attacker pre-dates and removes its own marker, at least two lock-user processes are waiting, coarse or matching modification times preserve the observation, and an honest contender creates a fresh marker on the reused inode, causing that live marker to be removed as stale. This issue is fixed in version 4.2.1.

CVSS Base Scores

version 3.1